On Fri, Jan 25, 2013 at 4:07 PM, Dave Kleikamp <[email protected]> wrote: > It looks like whatever data or metadata resides in that block is not an > inode extent. There really isn't a tool that examines a jfs filesystem > to determine what any particular block is being used as, but jfs_debugfs > is a really low-level tool that gives you the ability to look at certain > structures assuming that you know what resides at a certain location. In > this case it seems that you are trying to find an inode at some > arbitrary location that doesn't contain one. >
Should I just walk back the block number I use in the 'd' command until I get a valid inode value and presume it covers subsequent blocks (up until the next one that yields a valid inode value)? Craig. ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
