Re: kernel BUG at fs/btrfs/extent-tree.c:1755 (was: 1772)

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

 



Hello,

situation update: I realized I haven't tried "nospace_cache" yet, even
though I tried "clear_cache". "clear cache" doesn't help at all. On the
other hand, with "nospace_cache":

# mount /dev/hdb -odevice=/dev/hdc,nospace_cache /mnt/test
device label root devid 2 transid 56099 /dev/hdc
device label root devid 1 transid 56099 /dev/hdb
btrfs: disabling disk space caching
btrfs: unlinked 1 orphans
/ # btrfs: continuing balance
btrfs: relocating block group 776713797632 flags 4

It successfully mounts rw and continues the balance.

I'm still doing it all on qemu with "-snapshot" option, to keep HD
contents unmodified. Now the question is: should I try to mount it
"nospace_cache" for real, try to keep using it and see what happens, or is
anyone interested in debugging this problem further before I potentially
destroy the "evidence"?

Regards


--
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