ReiserFS
in [Slackware]
|
From: TheMaxer on 17 Jan 2008 07:43 Dear All, I've an older Slackware V10 setup, running linux 2.6.13 with ReiserFS. Everything works fine and therefore I haven't attempted to upgrade. however, there occasionally is a problem. When the system is in use and is powered off the hard way (so no shutdown -h now involved), the system will boot at new power up, notes that the FS is not clean, says the system appears to be mounted in read-only and then says skipping journal reply. However, there seems to be file corruptions and these lead to unexpected system lock-ups. How can I force a journal reply / FS check / recovery? Thanks
From: jjg on 17 Jan 2008 07:58 TheMaxer wrote: > Dear All, > > I've an older Slackware V10 setup, running linux 2.6.13 with ReiserFS. > Everything works fine and therefore I haven't attempted to upgrade. > however, there occasionally is a problem. When the system is in use > and is powered off the hard way (so no shutdown -h now involved), the > system will boot at new power up, notes that the FS is not clean, says > the system appears to be mounted in read-only and then says skipping > journal reply. However, there seems to be file corruptions and these > lead to unexpected system lock-ups. > > How can I force a journal reply / FS check / recovery? > > Thanks man reiserfsck
From: Giovanni on 17 Jan 2008 08:11 On 01/17/08 13:43, TheMaxer wrote: > I've an older Slackware V10 setup, running linux 2.6.13 with > ReiserFS. Everything works fine and therefore I haven't attempted > to upgrade. however, there occasionally is a problem. When the > system is in use and is powered off the hard way (so no shutdown -h > now involved), the system will boot at new power up, notes that the > FS is not clean, says the system appears to be mounted in read-only > and then says skipping journal reply. However, there seems to be > file corruptions and these lead to unexpected system lock-ups. > > How can I force a journal reply / FS check / recovery? Usually journal updates are applied after the file system is remounted read/write. If you really want the FS checked switch to run-level 1, unmount all fs, remount root fs in read-only and then you can fsck the root fs even if it is mounted. Other fs can fsck'ed after you unmount them. Ciao Giovanni -- A computer is like an air conditioner, it stops working when you open Windows. Registered Linux user #337974 < http://giovanni.homelinux.net/ >
From: jjg on 17 Jan 2008 11:06 Res wrote: > On Thu, 17 Jan 2008, jjg wrote: > >> TheMaxer wrote: >> >>> Dear All, >>> >>> I've an older Slackware V10 setup, running linux 2.6.13 with ReiserFS. >>> Everything works fine and therefore I haven't attempted to upgrade. >>> however, there occasionally is a problem. When the system is in use >>> and is powered off the hard way (so no shutdown -h now involved), the >>> system will boot at new power up, notes that the FS is not clean, says >>> the system appears to be mounted in read-only and then says skipping >>> journal reply. However, there seems to be file corruptions and these >>> lead to unexpected system lock-ups. >>> >>> How can I force a journal reply / FS check / recovery? >>> >>> Thanks >> >> man reiserfsck > > Thats not going to help him much :) > The problem is in the design. > Well, it depends... he has to unmount the volume to run a check on it... yes, if his whole file system is reiser, that might be a problem. In that case he might run a Knoppix live CD.
From: Keith Keller on 17 Jan 2008 12:47 On 2008-01-17, TheMaxer <max(a)max-irene.demon.nl> wrote: > > I've an older Slackware V10 setup, running linux 2.6.13 with ReiserFS. > Everything works fine and therefore I haven't attempted to upgrade. > however, there occasionally is a problem. When the system is in use > and is powered off the hard way (so no shutdown -h now involved), Perhaps you should stop doing that. ;-) Is there a reason you're not shutting down cleanly? Is it local power issues, or user education, or something else? > the > system will boot at new power up, notes that the FS is not clean, says > the system appears to be mounted in read-only and then says skipping > journal reply. However, there seems to be file corruptions and these > lead to unexpected system lock-ups. > > How can I force a journal reply / FS check / recovery? As others have mentioned, it seems like you need to boot to single-user and run reiserfsck manually. Another poster mentioned that you could fsck the root filesystem if mounted read-only, but for some filesystem problems fsck won't do a repair unless the filesystem is not mounted at all. If that's the case, you'll need to boot from a rescue disk (the Slackware CD should suffice) and run reiserfsck from there. I know this is a bit of a non sequitur, but Hans Reiser is in a bit of trouble. (Search sfgate.com for more details.) For that and other reasons (a reiserfsck on some of my large filesystems takes a lot longer than a comparable e2fsck), I've been moving away from reiserfs. XFS is another alternative to ext2 and reiserfs, which I've used but not extensively. --keith -- kkeller-usenet(a)wombat.san-francisco.ca.us (try just my userid to email me) AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt see X- headers for PGP signature information
|
Pages: 1 Prev: KDE vs. Bash Next: Dan C(unt) (was: Re: KDE vs. Bash (was:...)) |