similar to: 2.6.22-rc1 killed my ext3 filesystem cleanly unmounted

ext3 is having big problems on my x86-64 system. An ext3 partition has just gone crazy, with the following messages in dmesg: EXT3-fs error (device hda3): ext3_readdir: bad entry in directory #4603905: rec_len % 4 != 0 - offset=0, inode=2507704792, rec_len=42, name_len=0 Aborting journal on device hda3. ext3_abort called. EXT3-fs abort (device hda3): ext3_journal_start: Detected aborted journal

Hello, I had something interesting happen on a RH8 ext3 system I setup.I am at a loss to understand what happened. Info: This system has two IDE disks, partitioned identically, and the largest partition on each (/dev/hda3 and /dev/hdb3, 96GB each) was mirrored in a linux software RAID-1 configuration. It was running fine for many months. Then I updated the kernel and needed to reboot accordingly.

Hi everyone, I've been running Redhat 7.2 (new install) for about 2 weeks now without any problems, but today I was not so lucky. My system hung while I was trying to configure the kernel-source RPM using 'xconfig'. After rebooting the system, it seems that my whole ext3 file system is corrupted. I get the message: Mounting root filesystem EXT3-fs: ide0(3,3):couldn't mount

Guys, The other day while working on my old workstation it get frozen and after reboot I lost almost all data unexpectedly. I have a RAID1 configuration with LVM. 2 IDE HDDs. md0 .. store /boot (100MB) -------------------------- /dev/hda2 /dev/hdd1 md1 .. store / (26GB) /dev/hda3 /dev/hdd2 The only info that still rest in was that, that I restore after the fresh install. It seems that the

Guys, The other day while working on my old workstation it got frozen and after reboot I lost almost all data unexpectedly. I have a RAID1 configuration with LVM. 2 IDE HDDs. md0 .. store /boot (100MB) -------------------------- /dev/hda2 /dev/hdd1 md1 .. store / (26GB) -------------------------- /dev/hda3 /dev/hdd2 The only info that still rest in was that, that I restore after the fresh

Hello, I am having some trouble getting quota's to work. When I try to set the quota for a user, it does not show up when I run repquota. I am doing this on a Redhat (RHEL5) machine (I assume it is the same on Centos). I think I am missing a step, but this is what I am doing: (1) I add usrquota to the /etc/fstab file, then reboot LABEL=/home /home ext3 defaults,usrquota 1 2 (2) Verify

Hello, I have a perplexing problem. Im running Mandrake 10.0 and samba 3.0 setup as a domain controller. My client machines are XP Pro. I can join the domain and my "Homes" directory connects as it should. But that's all I can do. I have other shares that I can't access. For instance, I have a "downloads" share. Ive tried every conceivable setting but when I try

hi, i''ve tried xen 3.1 on my gentoo lastly but i can''t boot xen because of the message: VFS: cannot open root device "/dev/hda3" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0) i''ve used the tar source from xensource. so the kernel is 2.6.18-xen

Hey all, Had a power failure and subsequent ext3 disk corruptions. Attempting to fix, but not working. Its a 120 gig IDE disk, 3 partitions. /boot, /, and swap. Basically can't boot up since the box can't get to the system files in /usr/ or anything. So I'm booting off of a FC2 disk 1 in recovery mode and trying to fix the filesystem with e2fsck The boot partition cleaned up

Hi, "Mircea Popescu" <nufarul.alb at go.ro> schrieb am 29.01.02: > I have this problem: > I've partitioned my hard drive with PQMagic 7 in the following way: > hda1 - fat32 > hda2 - ext2 > hda3 - fat16 > hda4 - extended > hda5 - Linux Swap > hda6 - fat32 > hda7 - ext2 > hda8 - fat32 > > I've put syslinux on

I must profane ignorance of complicated filesystem stuff, so feel free to call me out here. Booting a root ext3 drive produces the following message at boot: kinit: trying to mount /dev/root on /root with type ext2 EXT2-fs warning (device hda3): ext2_fill_super: warning: mounting ext3 filesystem as ext2 When remounted rw by init, everything looks fine: $ mount | grep hda3 /dev/hda3 on / type

I have been trying very hard to seek help with my very complex issue but so far none have been successful. So I would like to try this mailing list, maybe there are some experts who know what they're talking about. Please refer to my experts-exchange question, all the required information will be there. It is more practical to send you to the webpage than paste out what I've done.

I'm using the ext3-patched version of Linux 2.4.13 (the patch from Andrew Morton's UOW site). I compiled both ext3 and ext2 into the kernel. I've also done "tune2fs -j /dev/hda3" and changed /etc/fstab to ext3. However, when I boot up, the filesystem still gets mounted as ext2. I've been trying to figure out why for many days now.. any ideas? Here's my setup:

'df' doesn't report my root partition, but does report my /boot partition when both are mounted with <type> auto. But when mounted with <type> ext3, both partitions are reported. Details: The system has mount-2.11m, tune2fs-1.25 and df (fileutils) 4.1 I just created an ext3 fs on a new Debian Woody install initially running linux-2.2.19 on ext2, but upgraded to

Hello All: My research group recently invested in a 17 node Linux rackmounted cluster. It was delivered recently and, being the lowly graduate student that I am, I was told to 'make sure that it works.' After investigating it, I noticed a problem with two of the hard drives one nodes 14 and 16. On most of the nodes, a 'df -hT' will give you the following: Filesystem Type Size

Hi there, I tried to setup my linux box with an ext3 root file system. That failed because of wrong initrd settings. Sorry. Now the filesystem is marked having a journal but there is no /.journal file anyway. I tried to buikd that journal by hand (tune2fs -j /dev/hda3 - in my case). That fails also. :-( /sbin/tune2fs -l /dev/hda3 says: ... Journal UUID: <none> Journal

I have a CentOS 4.2 system that was set up VERY quickly following the demise of its former life as a CentOS 3 server - you don't want the full story, but it had to be done quickly to get a company up and working following a slight disaster involving an electrician, a portable appliance safety tester and a pulled power cable - anyway, here's where I am at... Everything is running fine but

That's not a very good source, since it's only available to one person. On Fri, May 25, 2018 at 7:12 AM, Peter Moody <mindrot at hda3.com> wrote: > On Thu, May 24, 2018 at 9:09 PM, Yegor Ievlev <koops1997 at gmail.com> wrote: >> How can I revoke one SSH certificate without having to replace the >> root certificate and all certificates signed by it? > >

Dear all, I followed the instructions found on http://www.zip.com.au/~akpm/linux/ext3/ext3-usage.html to convert / on several of my boxes to ext3. Strange to me, on some boxes it perfectly worked while on others it didn't. One of the differences found is that on the ok-boxes mount reports: /dev/hda3 on / type ext3 (rw,errors=remount-ro) /* Settings: cat /etc/fstab /dev/hda3 / ext3

On Saturday I finally upgraded a machine from CentOS 4.3 (I think) to 4.5 via yum. Seemed to went fine. However, during the following night /home got mounted read-only because of an EXT3-fs error. The next night happened the same. Also, today, I saw the first-ever kernel crash on this machine. The machine is about three years old or so, went into production two years ago with CentOS 4.1 or so and