From: Miao Xie <miaox@cn.fujitsu.com>
To: Mitch Harder <mitch.harder@sabayonlinux.org>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 1/3] Btrfs: fix btrfsck error 400 when truncating a compressed file extent
Date: Mon, 09 Jan 2012 13:49:27 +0800 [thread overview]
Message-ID: <4F0A7FE7.5080705@cn.fujitsu.com> (raw)
In-Reply-To: <CAKcLGm9rzcAJL-MC9u7jQmQgiEAWR4FPCVALxJHVJJ=Q0_p9TQ@mail.gmail.com>
On Sun, 8 Jan 2012 22:45:14 -0600, Mitch Harder wrote:
> 2012/1/5 Miao Xie <miaox@cn.fujitsu.com>:
>> 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
prev parent reply other threads:[~2012-01-09 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 8:32 [PATCH 1/3] Btrfs: fix btrfsck error 400 when truncating a compressed file extent Miao Xie
2012-01-09 4:45 ` Mitch Harder
2012-01-09 5:49 ` Miao Xie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F0A7FE7.5080705@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mitch.harder@sabayonlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.