[Top] [All Lists]

Re: xfs_db

To: Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject: Re: xfs_db
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Tue, 16 Oct 2012 08:36:16 +1100
Cc: Anshul Kundra <anshul.kundra@xxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
In-reply-to: <507C766A.3000400@xxxxxxxxxxx>
References: <CACBF2D716C5104BAC48A16827DE5B1513576996C6@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <507C766A.3000400@xxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
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?


Dave Chinner

<Prev in Thread] Current Thread [Next in Thread>