| To: | Anshul Kundra <anshul.kundra@xxxxxxx> |
|---|---|
| Subject: | Re: xfs_db |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Mon, 15 Oct 2012 15:47:38 -0500 |
| Cc: | "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| In-reply-to: | <CACBF2D716C5104BAC48A16827DE5B1513576996C6@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <CACBF2D716C5104BAC48A16827DE5B1513576996C6@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 |
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. -Eric > > Thanks & Regards > > Anshul Kundra > > > |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Usage bigger after copy?, Wayne Walker |
|---|---|
| Next by Date: | Re: xfs_db, Dave Chinner |
| Previous by Thread: | xfs_db, Anshul Kundra |
| Next by Thread: | Re: xfs_db, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |