Re: [gentoo-user] fsck
On Saturday 05 March 2005 20:11, Peter Gordon wrote: > Julien Cayzac wrote: > > But reiserfs keeps telling me it can't replay the journal because it's > > read-only... > > Use a more mature filesystem? ^_^ > *runs and hides* Run far, hide deep deep down an enormous cave, don your asbestos suit and bear with the cancer thread. ;-) ;-) ;-) Just couldn't resist - like you. I have set up more boxes with ReiserFS than I care to count without such a problem on any of them. Something is wrong with his setup but I can't figure out what from his posting. :-( Uwe -- Alternative phrasing of the First Law of Thermodynamics: If you eat it, and you don't burn it off, you'll sit on it. http://www.uwix.iway.na (last updated: 20.06.2004) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] fsck
Julien Cayzac wrote: But reiserfs keeps telling me it can't replay the journal because it's read-only... Use a more mature filesystem? ^_^ *runs and hides* -- () The ASCII Ribbon Campaign - against HTML Email, /\ vCards, and proprietary formats. --- Peter A. Gordon (codergeek42) E-Mail: [EMAIL PROTECTED] GPG Public Key ID: 0x109DBECE GPG Key Fingerprint (SHA1): E485 E2F7 11CE F9B2 E3D9 C95D 208F B732 109D BECE Encrypted and/or Signed correspondence preffered. GPG Public Key available upon request or from pgp.mit.edu's public key server. --- signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] fsck
On Fri, 4 Mar 2005 21:45:10 -0800, John Myers <[EMAIL PROTECTED]> wrote: > the root filesystem is mounted by the kernel before it passes control to init, > as it needs to be able to *find* init. Also, the root filesystem must be > mounted in order to run fsck. But it doesn't have to be mounted read-write. > IIRC, when the kernel mounts the root, it mounts it read-only. You *can* fsck > a read-only fs. But reiserfs keeps telling me it can't replay the journal because it's read-only... -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] fsck
On Thursday 03 March 2005 21:25, A. Khattri wrote: > Think about this - if the checkfs script is running then root must already > be mounted. You shouldn't (can't?) fsck a mounted fs. Also if you look at > the startup scripts you will see that checkroot runs BEFORE checkfs so the > root file system has already been fsck'ed at that point by the checkroot > script. the root filesystem is mounted by the kernel before it passes control to init, as it needs to be able to *find* init. Also, the root filesystem must be mounted in order to run fsck. But it doesn't have to be mounted read-write. IIRC, when the kernel mounts the root, it mounts it read-only. You *can* fsck a read-only fs. -- t3h 3l3ctr0n3rd <[EMAIL PROTECTED]> Supermarket Deli Clerk and Student Programmer OpenPGP Key Fingerprint: 0A65 EEFA B23A F0AC E6C2 C71C BEA0 E055 BE0E EC25 pgpfRDpQAqMyq.pgp Description: PGP signature
Re: [gentoo-user] fsck
On Fri, 4 Mar 2005, Iain Buchanan wrote: > however, while looking into this, (because I noticed I haven't ever seen > the filesystem check when I shutdown uncleanly) I found > in /etc/init.d/checkfs: > > fsck -C -T -R -A -a > > now I'm happy with all of that except the -R, according to man fsck: > > -R When checking all file systems with the -A flag, skip the root > file system (in case it's already mounted read-write). > > Am I right when I read this as "don't even bother to try to check the > root fs"? Shouldn't it be rather "try to check the root fs unless its > mounted read-write"? Think about this - if the checkfs script is running then root must already be mounted. You shouldn't (can't?) fsck a mounted fs. Also if you look at the startup scripts you will see that checkroot runs BEFORE checkfs so the root file system has already been fsck'ed at that point by the checkroot script. -- AK -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] fsck
On Thu, 2005-03-03 at 23:50 +, Mike Williams wrote: > On Thursday 03 March 2005 23:05, A. Khattri wrote: > > You can also force a full fsck every time you boot by creating the file > > /forcefsck (e.g. "touch /forcefsck") when shutting down - the next time > > you restart it will do a full fsck of all disks. > > Not quite. You need to set the last field of each partition line in fstab to > a > number greater than 1, otherwise the forcefsck won't touch them. however, while looking into this, (because I noticed I haven't ever seen the filesystem check when I shutdown uncleanly) I found in /etc/init.d/checkfs: fsck -C -T -R -A -a now I'm happy with all of that except the -R, according to man fsck: -R When checking all file systems with the -A flag, skip the root file system (in case it's already mounted read-write). Am I right when I read this as "don't even bother to try to check the root fs"? Shouldn't it be rather "try to check the root fs unless its mounted read-write"? any thoughts? -- Iain Buchanan <[EMAIL PROTECTED]> -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] fsck
On Thursday 03 March 2005 23:05, A. Khattri wrote: > You can also force a full fsck every time you boot by creating the file > /forcefsck (e.g. "touch /forcefsck") when shutting down - the next time > you restart it will do a full fsck of all disks. Not quite. You need to set the last field of each partition line in fstab to a number greater than 1, otherwise the forcefsck won't touch them. -- Mike Williams pgpPxWW5RLLAe.pgp Description: PGP signature
Re: [gentoo-user] fsck
On Thu, 3 Mar 2005, pepone pepone wrote: > I use jfs for my home partition and if mount fails i want to aumatic run fsck > maybe i need same expecial option in fstab? > > /dev/hdc5 /home/peponejfs noatime Normally checkfs runs fsck BEFORE mounting a file system (file systems need to be unmounted for fsck to work on them), so your system probably already does this. In the old days this would be similar to the "preen" options which do some light cleanup of file systems. You can also force a full fsck every time you boot by creating the file /forcefsck (e.g. "touch /forcefsck") when shutting down - the next time you restart it will do a full fsck of all disks. -- A. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] fsck
I use jfs for my home partition and if mount fails i want to aumatic run fsck maybe i need same expecial option in fstab? /dev/hdc5 /home/peponejfs noatime 0 0 On Thu, 3 Mar 2005 15:14:28 -0500 (EST), A. Khattri <[EMAIL PROTECTED]> wrote: > On Thu, 3 Mar 2005, pepone pepone wrote: > > > Hello what is the correct way in gentoo for automatic check partitions > > that are not cleane unmounted > > If you reboot it will check the partitions if necessary (or use a journal > to make sure they are consistent). To do it manually, you should reboot > into single user mode and run fsck manually on the unmounted file-system > then bring the system up multi-user. > > -- > A. > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] fsck
On Thu, 3 Mar 2005, pepone pepone wrote: > Hello what is the correct way in gentoo for automatic check partitions > that are not cleane unmounted If you reboot it will check the partitions if necessary (or use a journal to make sure they are consistent). To do it manually, you should reboot into single user mode and run fsck manually on the unmounted file-system then bring the system up multi-user. -- A. -- gentoo-user@gentoo.org mailing list
[gentoo-user] fsck
Hello what is the correct way in gentoo for automatic check partitions that are not cleane unmounted -- gentoo-user@gentoo.org mailing list
[gentoo-user] fsck not seeing /etc/fstab?
Hi, I've ran into the fsck not finding /dev/ROOT /dev/BOOT problem. But the strange things is: the following is the /etc/fstab file, which is correctly setup AFAICT: Can anyone give me any hint on what other things might cause this problem. # NOTE: If your BOOT partition is ReiserFS, add the notail option to opts. /dev/sda1 /boot ext3noauto,noatime 1 1 /dev/sda3 / ext3noatime 0 0 /dev/sda2 noneswapsw 0 0 # NOTE: The next line is critical for boot! none/proc procdefaults 0 0 # glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for # POSIX shared memory (shm_open, shm_unlink). # (tmpfs is a dynamically expandable/shrinkable ramdisk, and will # use almost no memory if not populated with files) # Adding the following line to /etc/fstab should take care of this: none/dev/shmtmpfs defaults 0 0 -- Money can't buy everything. Sometimes money can't even buy a gun... -- gentoo-user@gentoo.org mailing list
