My past experience with jfs is that it was rock solid regardless of
power outages, etc
For a new project, I am running Fedora Core 4 Xen on Sun V20z's using
jfs for everything except /boot
While running lighttpd and some cvs updates on a partition, started
receiving errors - unfortunately, I only noticed when I got a msg that
the file system was read-only and I couldn't create/modify files.
I used fsck.jfs -f but hadnt read all the threads here and didnt do -v
The version that comes with FC 4 is 1.1.7, should I upgrade to 1.1.8?
Any other tips, run fsck -n via a cronjob periodically ?
TIA
messages:Sep 25 17:54:46 s1-vm101 kernel: JFS: nTxBlock = 6539, nTxLock
= 52313
messages:Sep 26 08:50:15 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 1
messages:Sep 26 08:50:15 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 2
messages:Sep 26 08:51:43 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 1
messages:Sep 26 08:51:43 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 2
messages:Sep 26 08:52:14 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 1
messages:Sep 26 08:52:14 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 2
messages:Sep 26 08:59:26 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 1
messages:Sep 26 08:59:26 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 2
messages:Sep 26 08:59:40 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 1
messages:Sep 26 08:59:40 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 2
messages:Sep 26 09:21:17 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 1
messages:Sep 26 09:21:17 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 2
messages:Sep 26 09:22:21 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 1
messages:Sep 26 09:22:21 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 2
messages:Sep 26 09:22:30 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 1
messages:Sep 26 09:22:30 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 2
messages:Sep 26 11:10:28 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 1
messages:Sep 26 11:10:28 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 2
messages:Sep 26 11:14:58 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 1
messages:Sep 26 11:14:58 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 2
messages:Sep 26 11:15:56 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 1
messages:Sep 26 11:15:56 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 2
messages:Sep 26 11:25:52 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 1
messages:Sep 26 11:25:52 s1-vm101 kernel: ERROR: (device sda2):
JFS:Dtree error: ino = 241811, bn=0, index = 2
messages:Sep 28 10:30:00 s1-vm101 kernel: ERROR: (device sda3):
XT_GETPAGE: xtree page corrupt
messages:Sep 28 10:30:48 s1-vm101 kernel: ERROR: (device sda3):
XT_GETPAGE: xtree page corrupt
messages:Sep 28 10:55:44 s1-vm101 kernel: ERROR: (device sda3):
XT_GETPAGE: xtree page corrupt
The first run of fsck:
# fsck.jfs -f /dev/sda3
fsck.jfs version 1.1.7, 22-Jul-2004
processing started: 9/28/2005 11.26.37
The current device is: /dev/sda3
Block size in bytes: 4096
Filesystem size in blocks: 6911966
**Phase 0 - Replay Journal Log
**Phase 1 - Check Blocks, Files/Directories, and Directory Entries
**Phase 2 - Count links
Incorrect link counts have been detected. Will correct.
**Phase 3 - Duplicate Block Rescan and Directory Connectedness
**Phase 4 - Report Problems
File system object FF4106 is linked as: error.log
cannot repair the data format error(s) in this file.
cannot repair FF4106. Will release.
File system object FF24579 is linked as:
/qa/xxx/server_xxx/conf/httpd-xxx.conf
cannot repair the data format error(s) in this file.
cannot repair FF24579. Will release.
File system object DF28672 is linked as: /xxx
cannot repair the data format error(s) in this directory.
cannot repair DF28672. Will release.
File system object FF28673 is linked as:
/qa/xxx/server_xxx/lib/perl/xxx/Config/xxx.pm
cannot repair the data format error(s) in this file.
cannot repair FF28673. Will release.
File system object FF28674 is linked as:
/qa/xxx/server_xxx/conf/httpd-xxx.conf
cannot repair the data format error(s) in this file.
cannot repair FF28674. Will release.
Fileset object DF28676: No paths found.
cannot repair the data format error(s) in this directory.
cannot repair DF28676. Will release.
Fileset object FF28678: No paths found.
cannot repair the data format error(s) in this file.
cannot repair FF28678. Will release.
Fileset object FF28680: No paths found.
cannot repair the data format error(s) in this file.
cannot repair FF28680. Will release.
Fileset object FF28681: No paths found.
cannot repair the data format error(s) in this file.
cannot repair FF28681. Will release.
Fileset object FF28682: No paths found.
cannot repair the data format error(s) in this file.
cannot repair FF28682. Will release.
Fileset object DF28704: No paths found.
File system object FF65554 is linked as:
/qa/xxx/server_xxx/bin/template-apache-heavy
cannot repair the data format error(s) in this file.
cannot repair FF65554. Will release.
File system object DF86791 is linked as:
/qa/xxx/server_xxx/lib/perl/xxx/Config
File system object FF86800 is linked as:
/qa/xxx/server_xxx/lib/perl/xxx/Config/xxx.old.pm
cannot repair the data format error(s) in this file.
cannot repair FF86800. Will release.
File system object FF86807 is linked as:
/qa/xxx/server_xxx/lib/perl/xxx/Config/CVS/Entries
cannot repair the data format error(s) in this file.
cannot repair FF86807. Will release.
File system object DF90153 is linked as: /qa/xxx/server_xxx/conf
**Phase 5 - Check Connectivity
**Phase 6 - Perform Approved Corrections
5 directories reconnected to /lost+found/.
9 files reconnected to /lost+found/.
**Phase 7 - Rebuild File/Directory Allocation Maps
**Phase 8 - Rebuild Disk Allocation Maps
27647864 kilobytes total disk space.
1140 kilobytes in 433 directories.
3808562 kilobytes in 2692 user files.
4 kilobytes in extended attributes
40514 kilobytes reserved for system use.
23799924 kilobytes are available for use.
Filesystem is clean.
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Jfs-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jfs-discussion
