From: "Lakshmipathi.G" <lakshmipathi.g@giis.co.in>
To: David Sterba <dsterba@suse.cz>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3] btrfs-progs: fsck-tests: verify 'btrfs check --repair' fixes corrupted nlink field
Date: Sat, 15 Apr 2017 14:39:21 +0530 [thread overview]
Message-ID: <20170415090921.GA5677@giis.co.in> (raw)
In-Reply-To: <20170330155211.GK4781@twin.jikos.cz>
On Thu, Mar 30, 2017 at 05:52:11PM +0200, David Sterba wrote:
> On Thu, Feb 02, 2017 at 01:35:02PM +0530, Lakshmipathi.G wrote:
> > Signed-off-by: Lakshmipathi.G <Lakshmipathi.G@giis.co.in>
> > ---
> > tests/fsck-tests/026-check-inode-link/test.sh | 30 +++++++++++++++++++++++++++
> > 1 file changed, 30 insertions(+)
> > create mode 100755 tests/fsck-tests/026-check-inode-link/test.sh
> >
> > diff --git a/tests/fsck-tests/026-check-inode-link/test.sh b/tests/fsck-tests/026-check-inode-link/test.sh
> > new file mode 100755
> > index 0000000..6822ee2
> > --- /dev/null
> > +++ b/tests/fsck-tests/026-check-inode-link/test.sh
> > @@ -0,0 +1,30 @@
> > +#!/bin/bash
> > +# verify that 'btrfs check --repair' fixes corrupted inode nlink field
> > +
> > +source $TOP/tests/common
> > +
> > +check_prereq btrfs-corrupt-block
> > +check_prereq mkfs.btrfs
> > +
> > +setup_root_helper
> > +prepare_test_dev 512M
>
> Please use default size unless you really need 512M for the test
> purposes.
>
> > +
> > +test_inode_nlink_field()
> > +{
> > + run_check $SUDO_HELPER $TOP/mkfs.btrfs -f $TEST_DEV
> > +
> > + run_check_mount_test_dev
> > + run_check $SUDO_HELPER touch $TEST_MNT/test_nlink.txt
> > +
> > + # find inode_number
> > + inode_number=`stat -c%i $TEST_MNT/test_nlink.txt`
> > + run_check_umount_test_dev
> > +
> > + # corrupt nlink field of inode object
> > + run_check $SUDO_HELPER $TOP/btrfs-corrupt-block -i $inode_number \
> > + -f nlink $TEST_DEV
> > +
> > + check_image $TEST_DEV
>
> The wrapper runs a pre-check that must detect errors, then runs --repair
> and then again a plain check. Is this intended here?
>
Yes its intentional. The test should fail, if its unable to detect the corruption.
This is to ensure btrfs-corrupt-block -f nlink works as expected.
> I think we should try to mount the fixed image again and read the file
> or check link count.
>
Right, I missed the verification part, will added this and change prepare_test_dev
to default size.
> Please add shell quotation around all variables.
Now quotation is added.
Cheers.
Lakshmipathi.G
prev parent reply other threads:[~2017-04-15 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 8:05 [PATCH v3] btrfs-progs: fsck-tests: verify 'btrfs check --repair' fixes corrupted nlink field Lakshmipathi.G
2017-03-30 15:52 ` David Sterba
2017-04-15 9:09 ` Lakshmipathi.G [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=20170415090921.GA5677@giis.co.in \
--to=lakshmipathi.g@giis.co.in \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).