Re: Btrfsck errors (fs tree 565 refs 125 not found) - how serious

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi again,

I am able to induce the btrfsck errors I experienced using a synthetic
workload on a fresh filesystem with linux-3.10.0.rc2.
However as filing the bug-report would take quite some time (uploading
512mb trace-files, writing a short read-me, ...) I wonder whether this
is an issue woth of reporting, or maybe just caused by an outdated
version of btrfsck (I am using
btrfs-progs-0.20.rc1.20130308git704a08c-1).

Regards, Clemens

> fs tree 565 refs 125 not found
>         unresolved ref root 807 dir 813347 index 277 namelen 39 name
> snapshot_1368273601_2013-05-11_14:00:01 error 600
  ......
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux