On Wed, 2005-03-16 at 08:12 +0100, Volker S�� wrote: > (Kernel 2.4.29 - jfsutils 1.1.7) > > Hi All! > > We have also in the last days a lvm-disk extended and than > > mount -o remount,resize > > It looks like no prob. But after about 20 hours we got this: > > Mar 9 17:59:42 ibm235 kernel: ERROR: (device lvm(58,0)): dtReadFirst: > btstack overrun > Mar 9 17:59:42 ibm235 kernel: btstack dump: > Mar 9 17:59:42 ibm235 kernel: bn = 0, index = 0 > Mar 9 17:59:42 ibm235 kernel: bn = 590018, index = 0 > Mar 9 17:59:42 ibm235 kernel: bn = 0, index = 0 > Mar 9 17:59:42 ibm235 kernel: bn = 590018, index = 0 > Mar 9 17:59:42 ibm235 kernel: bn = 0, index = 0 > Mar 9 17:59:42 ibm235 kernel: bn = 590018, index = 0 > Mar 9 17:59:42 ibm235 kernel: bn = 0, index = 0 > Mar 9 17:59:42 ibm235 kernel: bn = c0149df2000003e8, index = 1000 > > and the fs mounted readonly.
I haven't given a lot of attention to resizing lately, and I intend to test it more thoroughly when I find the time. Maybe I'll be able to recreate a similar problem and determine the cause. > An fsck on the readonly-mounted fs tells me: > > fsck.jfs version 1.1.7, 22-Jul-2004 > processing started: 3/9/2005 23.53.24 > Using default parameter: -p > The current device is: /dev/system/daten > Block size in bytes: 4096 > Filesystem size in blocks: 7766016 > **Phase 0 - Replay Journal Log > **Phase 1 - Check Blocks, Files/Directories, and Directory Entries > **Phase 2 - Count links > **Phase 3 - Duplicate Block Rescan and Directory Connectedness > Directory entries for unallocated files have been detected. Will remove. > **Phase 4 - Report Problems > File system object FF466944 is linked as: > /programme/Daten/wo2000/00001000/HMDVSTAT.ldb > cannot repair the data format error(s) in this file. > cannot repair FF466944. Will release. > File system object FF524288 is linked as: > /programme/Daten/00010406/rew/rew.ldb > The path(s) refer to an unallocated file. Will remove. > File system object FF532481 is linked as: /programme/winhmd/Lock/wml35.tmp > The path(s) refer to an unallocated file. Will remove. > **Phase 5 - Check Connectivity > **Phase 6 - Perform Approved Corrections > **Phase 7 - Rebuild File/Directory Allocation Maps > **Phase 8 - Rebuild Disk Allocation Maps > 31064064 kilobytes total disk space. > 43166 kilobytes in 10092 directories. > 20224277 kilobytes in 179210 user files. > 452 kilobytes in extended attributes > 130333 kilobytes reserved for system use. > 10752168 kilobytes are available for use. > Filesystem is clean. > > But after remount rw some errors occured again. > > At next we unmount the dev an run fsck on unmounted fs -> some errors > repaired an after mount rw -> no prob anymore.. > > Volker -- David Kleikamp IBM Linux Technology Center ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
