Re: [PATCH 1/3] Btrfs: fix btrfsck error 400 when truncating a compressed file extent

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

 



On Sun, 8 Jan 2012 22:45:14 -0600, Mitch Harder wrote:
> 2012/1/5 Miao Xie <miaox@xxxxxxxxxxxxxx>:
>> Reproduce steps:
>>  # mkfs.btrfs /dev/sdb5
>>  # mount /dev/sdb5 -o compress=lzo /mnt
>>  # dd if=/dev/zero of=/mnt/tmpfile bs=128K count=1
>>  # sync
>>  # truncate -s 64K /mnt/tmpfile
>>  root 5 inode 257 errors 400
> 
> Is this patch set intended to address the general case of btrfsck
> inode 400 errors, or is it intended for this specific case.
> 
> I've been picking up btrfsck inode 400 errors all over the place
> recently on unclean shutdowns, and I was wondering if this patch set
> might address the issue of unclean shutdowns, or if there is a more
> general COW regression out there (or if I'm just extremely unlucky).

The purpose of this patch set is to fix the bug of the left orphan items which
is caused by the truncation, not the general case of btrfsck 400 errors.

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