| View previous topic :: View next topic |
| Author |
Message |
Ma3oxuct
Guru
Joined: 18 Apr 2003
Posts: 523
|
 Posted: Sun Nov 12, 2006 5:19 pm Post subject: Filesystem trouble |
 |
|
Was attempting to emerge openoffice, and received an error saying that I have a read-only file system (I was able to write to it with no trouble a few minutes earlier). So I checked my /proc/mounts:
| Code: |
Ma3oxuct andrey # cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / jfs ro 0 0
proc /proc proc rw,nosuid,nodev,noexec 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec 0 0
udev /dev ramfs rw,nosuid 0 0
devpts /dev/pts devpts rw,nosuid,noexec 0 0
/dev/md1 /home jfs rw 0 0
/dev/md2 /rep xfs rw,sunit=128,swidth=384 0 0
/dev/md3 /in xfs rw,sunit=128,swidth=384 0 0
/dev/md4 /usr/portage jfs rw 0 0
/dev/md7 /work jfs rw 0 0
shm /dev/shm tmpfs rw,nosuid,nodev,noexec 0 0
usbfs /proc/bus/usb usbfs rw,nosuid,noexec 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec 0 0
|
And for some reason it says: /dev/root / jfs ro 0 0 instead of /dev/md5 / jfs rw 0 0.
Naturally I ran fsck.jfs /dev/md5 and am currently on this (I canceled the process):
| Code: |
Ma3oxuct andrey # fsck.jfs /dev/md5
fsck.jfs version 1.1.11, 05-Jun-2006
processing started: 11/12/2006 11.52.15
Using default parameter: -p
The current device is: /dev/md5
Block size in bytes: 4096
Filesystem size in blocks: 5859200
**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
|
This however scares me because a file system with incorrect link count is not a healthy file system. I had this happen with another partition yesterday (the /usr/portage one), and the fsck.jfs ended up messing up and putting more than 1/2 the file system in lost+found. I was not too worried about that partition because my system could function without it, so I simply re-formatted the partition and rebuilt the data in it. This partition, however, I cannot afford to lose. I have a November 6 backup of the partition to revert to, but this would require me to travel to where the server is to apply it.
Does anyone know of a safe way to save my root partition?
Note: The machine in question is not the one in my sig. |
|
| Back to top |
|
 |
Ma3oxuct
Guru
Joined: 18 Apr 2003
Posts: 523
|
| Posted: Sun Nov 12, 2006 6:12 pm Post subject: |
|
|
I ran fsck.jfs /dev/md5 -n, forcing it not to change anything on the file system.
And I get the following type of output:
| Code: | tem object FF447699 is linked as: fs/nls/nls_iso8859-2.mod.o
File claims cross linked block(s).
cannot repair FF447699.
File system object FF447700 is linked as: fs/nls/.nls_cp863.ko.cmd
File claims cross linked block(s).
cannot repair FF447700.
File system object FF447701 is linked as: fs/nls/.nls_iso8859-2.mod.o.cmd
File claims cross linked block(s).
cannot repair FF447701.
File system object FF447702 is linked as: fs/nls/nls_iso8859-2.ko
File claims cross linked block(s).
cannot repair FF447702.
File system object FF447703 is linked as: fs/nls/nls_iso8859-3.mod.o
File claims cross linked block(s).
cannot repair FF447703.
File system object FF447704 is linked as: fs/nls/.nls_cp865.ko.cmd
File claims cross linked block(s).
cannot repair FF447704.
File system object FF447705 is linked as: fs/nls/.nls_iso8859-3.mod.o.cmd
File claims cross linked block(s).
cannot repair FF447705.
File system object FF447706 is linked as: fs/nls/nls_iso8859-3.ko
File claims cross linked block(s).
cannot repair FF447706.
File system object FF447707 is linked as: fs/nls/nls_iso8859-4.mod.o
File claims cross linked block(s).
cannot repair FF447707.
File system object FF447708 is linked as: fs/nls/.nls_cp869.ko.cmd
File claims cross linked block(s).
cannot repair FF447708.
File system object FF447709 is linked as: fs/nls/.nls_iso8859-4.mod.o.cmd
File claims cross linked block(s).
cannot repair FF447709.
File system object FF447710 is linked as: fs/nls/nls_iso8859-4.ko
File claims cross linked block(s).
cannot repair FF447710.
File system object FF447711 is linked as: fs/nls/nls_iso8859-5.mod.o
File claims cross linked block(s).
cannot repair FF447711.
File system object FF447712 is linked as: fs/nls/.nls_iso8859-13.ko.cmd
File claims cross linked block(s).
cannot repair FF447712.
File system object FF447713 is linked as: fs/nls/.nls_iso8859-5.mod.o.cmd
File claims cross linked block(s).
cannot repair FF447713.
File system object FF447714 is linked as: fs/nls/nls_iso8859-5.ko
File claims cross linked block(s).
cannot repair FF447714.
|
I can still read the files. If I take off the -n option from fsck.jfs, I am sure that it will get rid of all those files (or most of the file on the partition).
| Code: | File system object FF1164509 is linked as: /usr/share/texmf/fonts/tfm/public/pl/plmi9.tfm
File claims cross linked block(s).
cannot repair FF1164509.
File system object FF1164510 is linked as: /usr/share/texmf/fonts/tfm/public/pl/plmib10.tfm
File claims cross linked block(s).
cannot repair FF1164510.
File system object FF1164511 is linked as: /usr/share/texmf/fonts/tfm/public/pl/plmib5.tfm
File claims cross linked block(s).
cannot repair FF1164511.
**Phase 5 - Check Connectivity
**Phase 6 - Perform Approved Corrections
**Phase 7 - Verify File/Directory Allocation Maps
Errors detected in the Fileset File/Directory Allocation Map control information. (F)
Errors detected in the Fileset File/Directory Allocation Map. (F)
**Phase 8 - Verify Disk Allocation Maps
Incorrect data detected in disk allocation structures.
Incorrect data detected in disk allocation control structures.
23436800 kilobytes total disk space.
108868 kilobytes in 35025 directories.
16756417 kilobytes in 413642 user files.
0 kilobytes in extended attributes
2398447 kilobytes reserved for system use.
4390804 kilobytes are available for use.
File system checked READ ONLY.
ERRORS HAVE BEEN DETECTED. Run fsck with the -f parameter to repair.
Filesystem is dirty.
|
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
