Re[2]: Rough (re)start with btrfs

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

 



Hello,

-by the way: I think my mail did not appear in the list, but only reached Chris and Qu directly. I just tried to re-send it. Could this be caused by
1) me not a subscriber of the list
2) combined with me sending attachments
I did *not* get any error message by the server.

 I was tempted to ask, whether this should be fixed. On the other hand, I
 am not even sure anything bad happened (except, well, the system -at
 least the copy- seemed to hang).

Definitely needs to be fixed.

With full dmesg, it's now clear that is a real dead lock.
Something wrong with the free space cache, blocking the whole fs to be
committed.

So, what's the next step? Shall I open a bug report somewhere, or is it already on some list?

If you still want to try btrfs, you could try "nosapce_cache" mount option.
Free space cache of btrfs is just an optimization, you can completely
ignore that with minor performance drop.

I will try that, yes.
Can you confirm, that it is unlikely, that I lost any data / damaged the Filesystem?

Regards,
Hendrik




[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