On 07/17/2012 09:20 PM, Tim Nufire wrote: > Hello, > > I'm having trouble repairing one of my volumes running JFS... Each time > I run jfs_fsck problems are found and repaired but yet the volume is > still marked dirty and the exit code is 4 (File system errors left > uncorrected). Here's the output from the last repair I did... > > Log of /sbin/jfs_fsck -f -y -v /dev/md10 > Tue Jul 17 07:21:08 2012 > > /sbin/jfs_fsck version 1.1.15.patched.2011.03.07, 04-Mar-2011 > processing started: 7/17/2012 7:21:08 > The current device is: /dev/md10 > Open(...READ/WRITE EXCLUSIVE...) returned rc = 0 > Primary superblock is valid. > The type of file system for the device is JFS. > Block size in bytes: 4096 > Filesystem size in blocks: 4756914448 > **Phase 0 - Replay Journal Log > LOGREDO: Log already redone! > logredo returned rc = 0 > **Phase 1 - Check Blocks, Files/Directories, and Directory Entries > Duplicate reference to 1 block(s) beginning at offset 4248749952 found > in file system object FF4086926. > Inode F4086926 has references to cross linked blocks. > File system object FF4086926 has corrupt data (39). > **Phase 2 - Count links > **Phase 3 - Duplicate Block Rescan and Directory Connectedness > Duplicate reference to 1 block(s) beginning at offset 4248749952 found > in file system object FF4086926. > Inode F4086926 has references to cross linked blocks. > **Phase 4 - Report Problems > File system object FF4086926 is linked as: > /20120713/08/08886904e6bbb5a731290014/h10/bzmf2108886904e6bbb5a7312900140000000000000000201207131025000000000240116.bzmf > File claims cross linked block(s). > cannot repair FF4086926. Will release. > **Phase 5 - Check Connectivity > **Phase 6 - Perform Approved Corrections > Superblock marked dirty because repairs are about to be written. > Directory inode F4086922 entry reference to inode F4086926 removed. > Storage allocated to inode F4086926 has been cleared. > **Phase 7 - Rebuild File/Directory Allocation Maps > **Phase 8 - Rebuild Disk Allocation Maps > Filesystem Summary: > Blocks in use for inodes: 2512268 > Inode count: 20098144 > File count: 11226660 > Directory count: 2153660 > Block count: 4756914448 > Free block count: 561778097 > 19027657792 kilobytes total disk space. > 6911782 kilobytes in 2153660 directories. > 16769576062 kilobytes in 11226660 user files. > 0 kilobytes in extended attributes > 0 kilobytes in access control lists > 17881124 kilobytes reserved for system use. > 2247112388 kilobytes are available for use. > *Filesystem is dirty.* > **** Filesystem was modified. **** > processing terminated: 7/17/2012 18:44:33 with return code: 0 exit > code: 4. > /sbin/jfs_fsck died with exit status 4 > > Tue Jul 17 18:44:37 2012 > ---------------- > > From the above it looks like all the problem found have been repaired so > I don't understand why the file system would still be dirty. Has anyone > else seen this? Should I just keep repairing it until it finally comes > back clean?
Is it reporting and fixing different problems each time, or is it attempting to fix the same thing over and over? It looks like it should be marking the file system clean since it claims to have fixed the problem, but obviously there are still problems. I can't recall seeing this problem before. > Thanks, > Tim ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
