Re: 5.2rc5 corruption, many "is compressed but inode flag doesn't allow"

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

 



On Tue, Jun 25, 2019 at 12:58 AM Nikolay Borisov <nborisov@xxxxxxxx> wrote:
>
> But why are your nocompress files being compressed?

$ sudo strace -p 624 -k -t -o sysdjourndstrace.txt
https://drive.google.com/open?id=1IspAjQ6b9dVizjqrX4E6ZErzUKH0CQBl

Maybe there's a better way to see what's going on. I do see chattr but
I don't know the value or the file. I wonder if the original file has
+C unset, then it's defragmented which somehow permits btrfs to
compress even though unsetting +C on a non-zero length file shouldn't
succeed, but then because it's written in a directory with +C the new
defragmented file inherits +C and gets no csums even though it's
compressed?

I'm throwing spaghetti at a wall though. (I know that's not a good way
to test spaghetti, so the analogy works perfectly.)


-- 
Chris Murphy



[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