You are not logged in.
Pages: 1
Whenever my machine boots I get this after starting UDev
jfs_fsck version 1.1.9, 04-Oct-2005
processing started: 10/11/2005 20.28.25
/dev/sda4 is mounted and the file system is not type JFS.
WARNING!!!
Running jfs_fsck on a mounted file system
or on a file system other than JFS
may cause SEVERE file system damage.
Do you really want to continue (y/n)?
If I press 'y' it works just fine and shutsdown just fine. Any ideas?
/etc/fstab#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /mnt/cd iso9660 ro,user,noauto,unhide 0 0
/dev/dvd /mnt/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /mnt/fl vfat user,noauto 0 0
/dev/sda4 / jfs defaults 1 1
/dev/sda2 swap swap defaults 0 0
/dev/sda3 /boot ext2 defaults 0 2
grub entry
# (0) Arch Linux
title Arch Linux
root (hd0,2)
kernel /vmlinuz root=/dev/sda4 ro
Offline
anything happen when you change dump and pass to 0 and 0?
Offline
Yeah that fixed it! Thanks! I'm curious though. If something happens, like an abnormal shutdown, will jfs_fsck run to replay the log at the next boot?
Offline
well, in /etc/rc.sysinit there's this line
[ -f /forcefsck ] && FORCEFSCK="-- -f"
if [ -x /sbin/fsck ]; then
stat_busy "Checking Filesystems"
/sbin/fsck -A -T -C -a $FORCEFSCK
so yes, I believe. I think your dump and pass was just screwing it up. The above commands check fstab entries sequentially and preform the checks that way.
Offline
Interesting. The computer hard-locked. Reboot and fsck didn't repair. I had to reboot with arch cd and manually do it.
Offline
I had the same problem ,downgrade to jfsutils 1.1.8 solved the problem.
Offline
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
If pass is 1 and dump is 0, does the problem disappear?
Offline
No. At least not here. I don't get the point why dump and pass set to 0 will avoide the question at boot, but tend to no cheching after errors.
pass number
Used by the fsck command to determine the order in which file system checks are done. The root file system should be specified with a pass number of 1, to be checked first, and other file systems should have larger numbers. (A file system with a pass number of zero is ignored by the fsck command.)
File systems within a drive should be assigned different pass numbers, but file systems on different drives can be checked on the same pass, to utilize possible parallelism available in the hardware. If pass number is not present, fsck checks each such file system sequentially after all eligible file systems with pass numbers have been checked.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
So...is there a workaround besides changing dump/pass to 0?
Offline
besides type "y" at boot? Not so far as I know.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
From the changelog at the jfsutils sourceforge site it looks like 1.1.10 solves the problem.
Offline
Indeed it does.
Offline
Pages: 1