Short form is that I used jfs_debugfs to query for inode info for block
135537084 using "d 135537084 0 i" and di_number was returned as a negative
value. I got the same value for iagnum using the command "d 135537084 0
I". What gives? Is this an instance of a note I found on the web about a
bug that would put a JFS error number in the inode and as a result corrupt
file data on the partition (for one file? for the directory containing the
affected file? for the whole partition?)?
Do I need to offload the files from the partition before taking any
corrective action? Should fsck fix the problem? Will I need to reformat
the partition to resolve this?
Any advice appreciated.
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
