Re: [PATCH v2 2/5] btrfs: initial fsverity support

Hi Boris, I love your patch! Yet something to improve: [auto build test ERROR on v5.12-rc2] [also build test ERROR on next-20210305] [cannot apply to kdave/for-next] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as do

Re[2]: Code: Bad RIP value.

Hello Nikolay, thank you. echo w > /proc/sysrq-trigger I assume, I need to do that soon after the problem occured? Is there a way to automate it? Otherwise, I will most likely only notice days after the occurence. Regarding the Kernel Version: I am using Debian, which usually delivers rathe

possible documentation bug[s]?

Hi all. *Long*-time Linux kernel hacker here, long-time storage-and-filesystems geek, new-ish to Btrfs. A few weeks ago I noticed some apparent intra-row conflicts [between "Size" and "Type" values] in the table at , so I

btrfs error: write time tree block corruption detected

Hi, Just noticed that one of my btrfs mounts on a server was in read-only mode. dmesg shows: [2217355.427810] BTRFS info (device sda3): scrub: started on devid 1 [2221262.216646] BTRFS info (device sda3): scrub: finished on devid 1 with status: 0 [2390153.679168] BTRFS info (device sda4): scrub:

Re: [PATCH v2] btrfs: fix lockdep warning while mounting sprout fs

David, Ping? Thanks, Anand On 04/03/2021 02:10, Anand Jain wrote: Following test case reproduces lockdep warning. Test case: DEV1=/dev/vdb DEV2=/dev/vdc umount /btrfs run mkfs.btrfs -f $DEV1 run btrfstune -S 1 $DEV1 run mount $DEV1 /btrfs run btrfs device add $DEV2 /btrfs -f run umount /b

Re: Code: Bad RIP value.

On 5.03.21 г. 21:57 ч., Hendrik Friedel wrote: > Hello, > > I am using linux 5.9.1 and have experienced tracebacks in conjunction > with btrfs and several filesystems: > btrfs fi show > Label: 'Daten'  uuid: c217331c-cf0c-49ae-86c7-48a67d1c346b >     Total devices 1 FS bytes used 54.69GiB >