Re: reiserfs annoyances
on Sun, Feb 04, 2001 at 01:13:08PM -0800, Jim Nutt ([EMAIL PROTECTED]) wrote: Matthew Sackman writes: Just to say that I've just switched most of my partitions over to reiserfs and am having exactely the same problems: the boot procedure halts on each boot-up because of the request for a file-system check on the root partition. I converted both my partitions to reiserfs (mainly because my laptop doesn't always wake up correctly and I hated waiting for fsck after hard reboots). I did a couple of things to get rid of the checks. First off, I removed the dump and pass parameters for the reiser partitions in fstab, ie., the entries for the reiser partitions look like this: It should only be necessary to set the 'pass' flag to zero. Dump relates to filesystem backups and is unrelated to boottime fsck. man 5 fstab. -- Karsten M. Self kmself@ix.netcom.comhttp://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org pgpilF5OqEBkz.pgp Description: PGP signature
Re: reiserfs annoyances
On Sun, Feb 04, 2001 at 08:52:36PM -0500, Dan Christensen wrote: Is there a way to convert an existing partition to reiserfs? Or does one have to create a new reiserfs partition and copy stuff over? Is there documentation outlining the procedure? Dan You have to have a spare partition and to be able to copy other partitions into it, reformat the original partition and then copy things back. This may mean that certain partitions can not be changed: if it's too big to be moved: you could try using tar and gzip or bzip2. Unless you have a spare partition then you may find yourself a bit stumped ;-) Matthew
Re: reiserfs annoyances
Just to say that I've just switched most of my partitions over to reiserfs and am having exactely the same problems: the boot procedure halts on each boot-up because of the request for a file-system check on the root partition. What is going on here? I figured that perhaps there was a problem with the kernel mounting the partition itself on bootup, and then having to unmount and remount the partition as rw (instead of ro), and so changed the read-only option in /etc/lilo.conf. But to no change. Surely more than three people must have a reiserfs root partiton? Could people please post their experiences and extracts of /etc/fstab please? Matthew On Sun, Feb 04, 2001 at 01:10:15AM +1100, Damon Muller wrote: Hi folks, I'm running a woody (as of 2-weeks ago) machine with a 2.4.1-ac2 kernel on it. I've got reiserfs compiled in, and all of my file systems (except boot) are now running on reiserfs. I'm running ii reiserfsprogs 3.x.0a-1 *PRE-RELEASE* Tools for ReiserFS filesystems compiled from the sid sources. Overally, I'm very happy with reiserfs, but there are a few annoyances. The first is that, presumably resiserfsck doesn't understand some option passed to it by /etc/init.d/checkroot.sh, as when it gets to that stage it stops and waits until you confirm to do an fsck. Does anyone know a way around this, short of commenting out the offending line in checkroot.sh (as is doing this a Bad Thing?)? The other thing that may or may not be a problem is that every time the system boots, it seems to replay the transaction logs of all of the filesystems. This suggests to me that it's not umounting them correctly. Or is this the expected behaviour of reiserfs? Another thing is it complains when you have the following in your /etc/fstab: /dev/hda2 / reiserfs defaults,errors=remount-ro 0 1 If you take out the `errors=remount-ro' it seems to work fine. Again, I'm not sure if removing this line is going to have disasterous consequences, or if it's something that reiserfs doesn't need. If anyone has any suggestions I'd be very interested. cheers, damon -- Damon Muller | Did a large procession wave their torches Criminologist/Linux Geek | As my head fell in the basket, http://killfilter.com | And was everybody dancing on the casket... PGP (GnuPG): A136E829 | - TBMG, Dead -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reiserfs annoyances
On Sun, Feb 04, 2001 at 07:45:56PM +, Matthew Sackman wrote: Just to say that I've just switched most of my partitions over to reiserfs and am having exactely the same problems: the boot procedure halts on each boot-up because of the request for a file-system check on the root partition. What is going on here? I figured that perhaps there was a problem with the kernel mounting the partition itself on bootup, and then having to unmount and remount the partition as rw (instead of ro), and so changed the read-only option in /etc/lilo.conf. But to no change. Surely more than three people must have a reiserfs root partiton? Could people please post their experiences and extracts of /etc/fstab please? /dev/sda3 / reiserfs defaults 1 1 /dev/sda1 /boot ext2 defaults 1 2 none /dev/pts devpts mode=0620 0 0 /mnt/cdrom /mnt/cdrom supermount fs=iso9660,dev=/dev/cdrom 0 0 /mnt/floppy /mnt/floppy supermount fs=vfat,dev=/dev/fd0 0 0 none /proc proc defaults 0 0 /dev/sda2 swap swap defaults 0 0 No problems at all. Stuart Matthew On Sun, Feb 04, 2001 at 01:10:15AM +1100, Damon Muller wrote: Hi folks, I'm running a woody (as of 2-weeks ago) machine with a 2.4.1-ac2 kernel on it. I've got reiserfs compiled in, and all of my file systems (except boot) are now running on reiserfs. I'm running ii reiserfsprogs 3.x.0a-1 *PRE-RELEASE* Tools for ReiserFS filesystems compiled from the sid sources. Overally, I'm very happy with reiserfs, but there are a few annoyances. The first is that, presumably resiserfsck doesn't understand some option passed to it by /etc/init.d/checkroot.sh, as when it gets to that stage it stops and waits until you confirm to do an fsck. Does anyone know a way around this, short of commenting out the offending line in checkroot.sh (as is doing this a Bad Thing?)? The other thing that may or may not be a problem is that every time the system boots, it seems to replay the transaction logs of all of the filesystems. This suggests to me that it's not umounting them correctly. Or is this the expected behaviour of reiserfs? Another thing is it complains when you have the following in your /etc/fstab: /dev/hda2 / reiserfs defaults,errors=remount-ro 0 1 If you take out the `errors=remount-ro' it seems to work fine. Again, I'm not sure if removing this line is going to have disasterous consequences, or if it's something that reiserfs doesn't need. If anyone has any suggestions I'd be very interested. cheers, damon -- Damon Muller | Did a large procession wave their torches Criminologist/Linux Geek | As my head fell in the basket, http://killfilter.com | And was everybody dancing on the casket... PGP (GnuPG): A136E829 | - TBMG, Dead -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reiserfs annoyances
On Sun, 4 Feb 2001, Matthew Sackman wrote: Just to say that I've just switched most of my partitions over to reiserfs and am having exactely the same problems: the boot procedure halts on each boot-up because of the request for a file-system check on the root partition. I don't know if this helps, but here is my fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass /dev/discs/disc0/part1 / ext2defaults0 1 /dev/discs/disc0/part10 noneswapsw 0 0 proc/proc procdefaults0 0 /dev/discs/disc0/part2 /boot ext2rw 0 2 /dev/discs/disc0/part5 /usrreiserfsrw 0 0 /dev/discs/disc0/part6 /usr/local ext2rw 0 2 /dev/discs/disc0/part7 /home reiserfsrw 0 0 /dev/discs/disc0/part8 /varreiserfsrw 0 0 /dev/discs/disc0/part9 /tmpreiserfsrw 0 0 /dev/discs/disc1/part1 /storage-1 vfatrw 0 2 /dev/discs/disc2/part1 /storage-2 reiserfsrw 0 0 /dev/discs/disc3/part1 /mnt/win2k autoro,user,noauto,uid=ian,gid=ian 0 0 /dev/discs/disc0/part4 /mnt/win2k-boot autorw,user,noauto,uid=ian,gid=ian 0 0 /dev/floppy/0 /floppy autodefaults,user,noauto0 0 /dev/cdroms/cdrom0 /dvdiso9660 defaults,ro,user,noauto 0 0 /dev/cdroms/cdrom1 /cdrw iso9660 defaults,user,noauto0 0 /storage-2/SWAP noneswapsw 0 0 none/dev/shmshm defaults0 0 Notice how I have the last field (pass) set at 0 for all reiserfs partitions? Ian
Re: reiserfs annoyances
Matthew Sackman writes: Just to say that I've just switched most of my partitions over to reiserfs and am having exactely the same problems: the boot procedure halts on each boot-up because of the request for a file-system check on the root partition. I converted both my partitions to reiserfs (mainly because my laptop doesn't always wake up correctly and I hated waiting for fsck after hard reboots). I did a couple of things to get rid of the checks. First off, I removed the dump and pass parameters for the reiser partitions in fstab, ie., the entries for the reiser partitions look like this: /dev/discs/disc0/part3 / reiserfsdefaults /dev/discs/disc0/part3 /mp3reiserfsdefaults (gee what do you think is on the second partition?) Anyway, I'm also using devfs, so that's why the device entries look a bit funky. This got rid of the checks for the at least the non-root partitions. I thought I had to do something else for the root partition, but I can't find the change now and can't remember what it was sigh. I don't have any problems with the questions now. jim
Re: reiserfs annoyances
Hi,
I just started using reiserfs (not for my important partitions yet),
it seems that the check takes place without the pass entry in fstab,
though I'm not certain.
from dmesg:
reiserfs: checking transaction log (device 08:06) ...
Using r5 hash to sort names
reiserfs: using 3.5.x disk format
ReiserFS version 3.6.25
reiserfs: checking transaction log (device 08:22) ...
Using r5 hash to sort names
reiserfs: using 3.5.x disk format
ReiserFS version 3.6.25
reiserfs: checking transaction log (device 08:07) ...
Using tea hash to sort names
reiserfs: using 3.5.x disk format
ReiserFS version 3.6.25
in fstab:
/dev/sda6 /tmp reiserfs defaults 0 0
/dev/sdc2 /Audio reiserfs defaults 0 0
/dev/sda7 /windows reiserfs defaults 0 0
/dev/sdb2 /scratch reiserfs defaults,user,noauto 0 0
I also hacked a non-interactive reiserfsck in /etc/init.d/checkfs.sh,
it's ugly but works:
snip
#KLUDGE by [EMAIL PROTECTED] DON'T DISTRIBUTE, it's embarasing
echo Checking ReiserFS file systems...
REISERS=`grep reiserfs /etc/fstab|/bin/awk '{print $1}'`
echo yes /tmp/reiser-checkp
for i in $REISERS;
do reiserfsck $i /tmp/reiser-checkp;
done;
rm /tmp/reiser-checkp
# Back to your regularly scripted init file
echo Checking all file systems...
/snip
Note I don't take my own advisory against redistributing, so I suppose
you needn't either now that it's publicly achived all over the net.
Looking at the dmesg output (which comes before this check), I think
this is probably unnecessary. No luck verifying this in the docs,
suppose it's time to look at the source code...
-Jon
Re: reiserfs annoyances
Yes, this works - removing the pass and dump parameters for ReiserFs disks stops the forced checking of the partitions. However, having defaults,errors=remount-ro still causes an error: unrecognised mount options. So I guess the errors=remount-ro bit is being passed to reiserfs as I don't get this message when I remove that bit. Many thanks, Matthew On Sun, Feb 04, 2001 at 01:13:08PM -0800, Jim Nutt wrote: Matthew Sackman writes: Just to say that I've just switched most of my partitions over to reiserfs and am having exactely the same problems: the boot procedure halts on each boot-up because of the request for a file-system check on the root partition. I converted both my partitions to reiserfs (mainly because my laptop doesn't always wake up correctly and I hated waiting for fsck after hard reboots). I did a couple of things to get rid of the checks. First off, I removed the dump and pass parameters for the reiser partitions in fstab, ie., the entries for the reiser partitions look like this: /dev/discs/disc0/part3/ reiserfsdefaults /dev/discs/disc0/part3/mp3reiserfsdefaults (gee what do you think is on the second partition?) Anyway, I'm also using devfs, so that's why the device entries look a bit funky. This got rid of the checks for the at least the non-root partitions. I thought I had to do something else for the root partition, but I can't find the change now and can't remember what it was sigh. I don't have any problems with the questions now. jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reiserfs annoyances
Is there a way to convert an existing partition to reiserfs? Or does one have to create a new reiserfs partition and copy stuff over? Is there documentation outlining the procedure? Dan
reiserfs annoyances
Hi folks, I'm running a woody (as of 2-weeks ago) machine with a 2.4.1-ac2 kernel on it. I've got reiserfs compiled in, and all of my file systems (except boot) are now running on reiserfs. I'm running ii reiserfsprogs 3.x.0a-1 *PRE-RELEASE* Tools for ReiserFS filesystems compiled from the sid sources. Overally, I'm very happy with reiserfs, but there are a few annoyances. The first is that, presumably resiserfsck doesn't understand some option passed to it by /etc/init.d/checkroot.sh, as when it gets to that stage it stops and waits until you confirm to do an fsck. Does anyone know a way around this, short of commenting out the offending line in checkroot.sh (as is doing this a Bad Thing?)? The other thing that may or may not be a problem is that every time the system boots, it seems to replay the transaction logs of all of the filesystems. This suggests to me that it's not umounting them correctly. Or is this the expected behaviour of reiserfs? Another thing is it complains when you have the following in your /etc/fstab: /dev/hda2 / reiserfs defaults,errors=remount-ro 0 1 If you take out the `errors=remount-ro' it seems to work fine. Again, I'm not sure if removing this line is going to have disasterous consequences, or if it's something that reiserfs doesn't need. If anyone has any suggestions I'd be very interested. cheers, damon -- Damon Muller | Did a large procession wave their torches Criminologist/Linux Geek | As my head fell in the basket, http://killfilter.com | And was everybody dancing on the casket... PGP (GnuPG): A136E829 | - TBMG, Dead
Re: reiserfs annoyances
Damon Muller wrote: The first is that, presumably resiserfsck doesn't understand some option passed to it by /etc/init.d/checkroot.sh, as when it gets to that stage it stops and waits until you confirm to do an fsck. Does anyone know a way around this, short of commenting out the offending line in checkroot.sh (as is doing this a Bad Thing?)? I don know the answer for that. The other thing that may or may not be a problem is that every time the system boots, it seems to replay the transaction logs of all of the filesystems. This suggests to me that it's not umounting them correctly. Or is this the expected behaviour of reiserfs? As far as I know it is normal, just to check the log, and make sure everything went fine with unmount. Thus, once it is done with the check, the file system should be without errors. Otherwise a journaled file system does not make sense. /dev/hda2 / reiserfs defaults,errors=remount-ro 0 1 Because the filesystem will be in good shape, the error-statement does not make sense. It is just a ext2 issue. (when fsck tells, the file system is corrupt it just mounts it read only. Added my rambling :-) Ciao, mattHias -- __ _ __ * /\_/\ \ \_/ \_/ / * Matthias Wieser * / \ \ /* ICQ#: 12597522 * / /\_/\ \ \_/^\_/ *[EMAIL PROTECTED] * WW WW *
Re: reiserfs annoyances
On Sat, Feb 03, 2001 at 05:05:29PM +0100, Matthias Wieser wrote: /dev/hda2 / reiserfs defaults,errors=remount-ro 0 1 Because the filesystem will be in good shape, the error-statement does not make sense. It is just a ext2 issue. (when fsck tells, the file system is corrupt it just mounts it read only. that is not correct, errors=remount-ro is a kernel mount option, if the kernel detects any sort of error when dealing with the filesystem it will remount it readonly to hopefully prevent further damage. i had this happen with kernel 2.2.13 when it started puking all over the filesystems. this type of option would still be useful on a journaled filesystem since journaling does absolutely NOTHING to protect you from buggy kernel filesystem code. -- Ethan Benson http://www.alaska.net/~erbenson/ pgpIfAnL7rigp.pgp Description: PGP signature
