similar to: RFC: ext3 ability to syslog actions

Forgive me if this has been discussed. I'm new to the list. I've just today installed ext3 .5d in my machine. All drives (including '/'). I like it! However, I'm curious about what it's doing. I don't know C, so telling me to read source won't help. I'm wondering if it would make sense to provide a facility (probably at the VFS level so that all filesystems

I had a power-fail this morning, and when I rebooted, /etc/rc.d/rc.boot issued a 'mount -n -o remount,ro /' and then a 'fsck -A -V -a -C'. The fsck failed on my root partition. I know why it failed. It called fsck.ext2 . My root poartition is ext3. My question is, why did it call fsck.ext2? Another question, why was it checked at all? My /etc/fstab contains: /dev/hda1 / ext3

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If ext3 is compiled in, how can you tell which version it is? For example, how can I log into the systems I admin and tell if they are ext3 6b or 7a? - -- Douglas J. Hunley (Linux User #174778) http://hunley.homeip.net/ http://linux.nf/ Adults are just kids who owe money. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For

I am installing Dovecot-2.1.13 on Slackware 13.37.0 for the first time to replace ipop3d and I have overcome all of the roadblocks as they have developed except this last one and I finally have to say ?uncle?. The error messages that are showing up in the dovecot.log are as follows. Jan 24 12:27:27 tux2 dovecot: auth: Error: passwd-file /etc/shadow: open(/etc/shadow) failed: Permission denied

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Have *ALL* the filesystem corruption issues that plague(d?) HTREE on 2.4.x cleaned up for 2.6? I believe they have, but before I enable this feature again, I'd like to be sure. Thanks. - -- Douglas J Hunley (doug at hunley.homeip.net) - Linux User #174778 http://doug.hunley.homeip.net && http://www.linux-sxs.org A day without sunshine

how can I prevent the 'EXT3-FS: mounted / in ordered-data mode' messages? they're cluttering my boot screen ;) thanks! -- Douglas J. Hunley (doug@hunley.homeip.net) - Linux User #174778 Admin: http://hunley.homeip.net/ Admin: http://linux.nf/ Brainbench Linux Administration Certified ~~ Now offering Linux admin services for the home user ~~ Linux: The OS people choose without

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Right now, every release of e2fsprogs, I do the following: ./configure --enable-elf-shlibs && make && make install rm config.cache && rm config.status ./configure && make install-libs Are these two seperate steps necessary? Seems to me that I had a problem installing something or other and it suggested the first line.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 does this version need to be patched for any reason to handle/work with ext3? I found a patch for the previous release of util-linux, but it don't apply cleanly to this version. thanks! - -- Douglas J. Hunley (Linux User #174778) http://hunley.homeip.net/ http://linux.nf/ As a SysAdmin, yes, I CAN read your e-mail, but I DON'T get that

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I created all my ext3 partitions a while back, so the journal.dat file is visable. I'd like to remove them and use the new tune2fs functionality. Can I just mount the drives as ext2, rm journal.dat, tune2fs -j /dev/hd?? and then remount as ext3? Or am I missing something? thanks! - -- Douglas J. Hunley (Linux User #174778)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 subject about says it all. should this only be done once per device or periodically? thanks! - -- Douglas J Hunley (doug at hunley.homeip.net) - Linux User #174778 Admin: Linux StepByStep - http://www.linux-sxs.org and http://jobs.linux-sxs.org Illiterate? Write for help! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 14 June 2001 13:05, Rick Sivernell babbled: > Doug > > Educate me please. What is the diff between ext2 & 3. I am using reiserfs > now and do like it. But I do like to have the stuff going, if I can. Be warned, I know nothing about reiserfs other than what I've read. short version: ext3 is a further development of

Just out of curiosity: Is htree in 2.6.0-test11 ? -- Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt@charite.de Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-916 Referat V a - Kommunikationsnetze - AIM. ralfpostfix

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been asked whether there are any outstanding issues in using dump/restore to backup ext3-based systems. The persons asking me this had mentioned previously hearing that dump may be unreliable and was asking for verifcation. TIA. - -- Douglas J Hunley (doug at hunley.homeip.net) - Linux User #174778 Admin: Linux StepByStep -

got the following in the freshmeat newsletter. the page doesn't say anything about it. also the sct dir on kernel.org still shows the WIP version... [007] - e2fsprogs 1.20 (Default)   by P. Adami (http://freshmeat.net/users/ramirez/)   Monday, May 28th 2001 19:39 The ext2fsprogs package contains essential ext2 filesystem utilities which consists of e2fsck, mke2fs, debugfs, dumpe2fs, tune2fs,

I managed to install 0.5d today. Got all 3 of my mounts converted (even '/' though it was a pain in the ass). Now on boot, I see: mounted /dev/hda1 on / EXT3-fs: mounted filesystem with ordered data mode and the exact same thing for /dev/hda3 and /dev/hdb1. they all come up and appear to be working. so is this normal? Or did I manage to screw up somewhere? -- Douglas J. Hunley (Linux User

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I applied this patch last night, installed e2fsprogs 1.30WIP, and now am seeing the following periodically in my logs: VFS: brelse: Trying to free free buffer issue? or not? - -- Douglas J Hunley (doug at hunley.homeip.net) - Linux User #174778 Admin: Linux StepByStep - http://www.linux-sxs.org and http://jobs.linux-sxs.org gethostbyintuition()

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In additin to the 'brelse' issue I mentioned a few days back, I'm seeing new messages in my logs about ext3 trying to unlink non-existant files. any ideas? log mesages are below: Oct 5 19:34:40 linux-sxs kernel: EXT3-fs warning (device sd(8,19)): ext3_unlink: Deleting nonexistent file (1433981), 0 Oct 5 19:38:32 linux-sxs kernel: VFS:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 14 June 2001 15:58, Stephen C. Tweedie babbled: > ext3 can do both metadata-only and full data journaling. You can > enable data journaling for the entire filesystem or on a per-file > basis (ext3 uses that functionality internally to journal writes to > the quota files to keep them consistent, for example.) I learn

Over the last two days we've been seeing a fair bit of this: ---- # ls -laR > /dev/null ... ls: ./server2/b/user/bxyz/392.: Input/output error ---- This is with the latest htree patches applied to 2.4.19, and latest e2fsprogs-test, on a dual AMD system, with 5x73GB SCSI drives on a MegaRAID controller. We're using the gcc 2.96 that comes with RH7.3. esfsck shows "Inodes that

---------- Forwarded Message ---------- Subject: ext3 for 2.4 Date: Thu, 17 May 2001 21:20:38 +1000 From: Andrew Morton <andrewm@uow.edu.au> To: ext2-devel@lists.sourceforge.net, "Peter J. Braam" <braam@mountainviewdata.com>, Andreas Dilger <adilger@turbolinux.com>, "Stephen C. Tweedie" <sct@redhat.com> Cc: linux-fsdevel@vger.kernel.org Summary: