From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>,
Anshul Kundra <anshul.kundra@hcl.com>
Subject: Re: xfs_db
Date: Tue, 16 Oct 2012 08:36:16 +1100 [thread overview]
Message-ID: <20121015213616.GD2739@dastard> (raw)
In-Reply-To: <507C766A.3000400@sandeen.net>
On Mon, Oct 15, 2012 at 03:47:38PM -0500, Eric Sandeen wrote:
> On 10/15/12 9:34 AM, Anshul Kundra wrote:
> > Suppose in XFS file system I want to corrupt a inode of my choice,
> > will it be possible using xfs_db
> >
> > Xfs_db blockget < inode number > blocktrash < seed value and type of
> > block >
> >
> > In the manuals it is written that it takes a random inodes for the
> > corruption which it does in actual practice, so can I use any
> > specific command to corrupt the inode (131 )
>
> As the manual says, blocktrash trashes random metadata blocks (possibly
> of specified type).
>
> You can, however, write whatever you want into various fields of
> inode 131 via xfs_db, there's just no built-in random method to
> do that.
A better question might be: "why do you want to corrupt a specific
inode"? To test repair, or online detection, or something else?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-10-15 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 14:34 xfs_db Anshul Kundra
2012-10-15 20:47 ` xfs_db Eric Sandeen
2012-10-15 21:36 ` Dave Chinner [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-20 17:11 XFS_DB Anshul Kundra
2013-02-21 11:27 ` XFS_DB Stefan Ring
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=20121015213616.GD2739@dastard \
--to=david@fromorbit.com \
--cc=anshul.kundra@hcl.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/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