similar to: Re: Root vulnerabilities in Linux

Hi. I was using 2.4.10 with ext3 0.9.10 and thought it was time to use -ac for the first time because 2.4.12-ac3 includes 0.9.12. I don't know what I did to get the following messages, but in my last boot I removed /etc/mtab (at runtime) and made it a symlink to /proc/mounts. Not sure if a bad idea, but the only problem until I rebooted was the need of losetup -d. When I rebooted, all

Does ctrl+c work? My experience with (non klibc) init=/bin/bash is that getting ctrl+c to work requires some jumping through hoops, because running as pid 1 doesn't really work. If I recall correctly you have to call setsid, and open a tty as a controlling tty, you can't call setsid as pid 1. The hack that I got to work (for reference, I'm using this for raw kernel testing

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

Hi, I'm running kernel 2.6.8-15, lvm2 v2.01.04-5 and acl v2.2.23-1 on a Sunblade 100 (sparc). In a few months we have experienced for several times that an ext3 filesystem is remounted as read-only (this is due to the option "errors=remount-ro" in /etc/fstab). Sometimes there is no error in log files but sometimes we see: kernel: init_special_inode: bogus i_mode (3016) kernel:

Hi, Apologies, this is going to be quite long - I'm going to provide as much info as possible. I'm running a system with ext3 fs on software RAID. The RAID set-up is as shown below: jlm@nijinsky:~$ cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid5] read_ahead 1024 sectors md0 : active raid1 hdc1[1] hda1[0] 96256 blocks [2/2] [UU] md5 : active raid1 hdk1[1] hde1[0]

Hi all, I'm trying to resize a journal on my root filesystem. This is Ext3, kernel 2.4.19, latest e2fsprogs + htree patch. I've remounted my root filesystem as ext2, but still when I 'tune2fs -O ^has_journal' I get ---- The has_journal flag may only be cleared when the filesystem is unmounted or mounted read-only. ---- So, how can I increase the size of the journal? I

[ adding klibc ml to cc ] On Thu, Feb 01, 2007 at 09:29:52AM -0600, John Goerzen wrote: > > It appears to be largely undocumented, but a review of > /usr/share/initramfs/scripts/nfs shows that this package supports NFSv2 > and v3 only. I don't know why v4 isn't supported. yup, this needs nfs v4 support in klibc nfsmount. would be could to get that soon postetch, but someone

Hi, We have software raid level 5 using 6 IDE disks amounting to about 500Gb. Its an ext3 filesystem which is NFS exported to a number of other machines. Recently, after running /etc/init.d/nfs-kernel-server stop /etc/init.d/nfs-common stop /etc/init.d/nfs-common start /etc/init.d/nfs-kernel-server start the whole raid array is gone. The file system is consistent and is the right size but no

Hi, I'm running a production server (Debian Sarge install) whose root filesystem (a software raid 1 array of 2 partitions of IDE drive) exhibited the following problem: Oct 28 06:00:06 server2 kernel: attempt to access beyond end of device Oct 28 06:00:06 server2 kernel: md2: rw=1, want=3050401328, limit=16353920 [...] a few of the above line snipped, want is different each time Oct 28

Hello everyone, I've just lost my whole EXT3 linux partition by what was probably a bug. For your reading pleasure, and in the hope there is enough information to fix this problem in the future, here the story of a violent ending: This tragic history starts actually on windows: MS Word had wiped out an important file on a floppy, and I got the task of retrieving what was possible. Using

Kernel 2.4.8 on an Athlon 500. e2fsprogs-1.23 ext3 compiled as a module. I used "tune2fs" to make /boot and /home into ext3, and remounted them OK. (I am so amazed to see the system come right back without an lengthy fsck on these two file systems after a power off! Well done!) I also used "tune2fs -j" on /, it created a /.journal file. The debugfs features command shows

On Fri, Sep 11, 2020 at 10:53:14AM +1000, Philip Rhoades via rsync <rsync at lists.samba.org> wrote: > Roland, > > > On 2020-09-10 21:27, Roland wrote: > > > with rsync hanging - after breakout on /home for writing I then get: > > > "Read-only file system" > > > > if your filesystem switches to read-only, you have a serious problem >

I have a CentOS 5 machine with an external 500G USB disk, formatted with JFS. How do I get this to mount automatically at boot time? If I add to /etc/fstab: /dev/sdb1 /var/video jfs defaults 1 2 fsck.jfs complains at boot time: Error: Cannot open device /dev/sdb1 Usage: fsck.jfs ... ... Give root password for maintenance ... If I log in with the root password, /dev/sdb1 is present, and I

Hi, This happened to me repeatedly (but not always), even after updating to the latest RELENG_7 yesterday ... 1. Boot into single user mode 2. fsck / # finishes successful! 3. mount -u / 4. Do a few edits to files in /etc 5. mount -u -o ro / softdep_waitidle: Failed to flush worklist for 0xc1f36b30 mount: /dev/ad0s1a : Device busy I can't remount the root file system read-only, so

Hello. We have, over the last few months, lost ext3 filesystems three times. The whole filesystem left unusable. nfs-server:~# mount /dev/rd/c0d1p1 /mnt -t ext3 mount: wrong fs type, bad option, bad superblock on /dev/rd/c0d1p1, or too many mounted file systems (in dmesg) EXT3-fs: journal inode is deleted. EXT3-fs: get root inode failed nfs-server:~# fsck /dev/rd/c0d1p1 Parallelizing

I've turned my root filesystem to ext3 and also changed the filesystem type in /etc/fstab. I initiated a powerfailure and watched booting. But the kernel mounted root filesystem first read only as ext2 and does than a fsck for ext2. The over partition, /boot and /vol1 (also ext3), are handled as ext3. After booting all partitions, also /, were mounted as ext3. But why root is checked as ext2?

Hi, yesterday I upgraded my kernel to 2.4.15-pre6 (after months of using only ac-kernels) and had my first ext3-error since 0.0.3 . syslog tells me : Nov 20 18:16:31 enterprise kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #47390: inode out of bounds - offset=0, inode=404363549, rec_len=4096, name_len=23 and the system remounted /usr to ro. I don't have

Hello, I have a 1.3TB ext3 filesystem that has been in service for about 3 months. About 6 days ago the Emulex fibrechannel controller logged a SCSI error and the filesystem changed to RO. It appears that the filesystem instantly changes to RO and prevents the journal from working, therefore invalidating the filesystem. The filesystem was unmounted and a remount was attempted. The mount failed

Hi I am using ext3 on Smoothwall Express 2 firewall, which I understand is based originally off Red Hat. The machine runs headless, without a monitor. On one ocassion booting stopped, hooking up a monitor revealed this, -- console output -- /dev/harddisk4 has been mounted 29 times without being checked, check forced. /dev/harddisk4: Optimizing directories: 47165 140835 /dev/harddisk4: *****

Hi, This is probably way far unsupported, but here goes: I had been running ext3 0.0.3b for a while and found that I wanted to convert back to ext2 so I could still play with 2.4test kernels. Here is what I did: 1) boot the machine with kernel args init=/bin/bash 2) run debugfs on the root partition to remove the have_journal ext2 feature flag. 3) remount the root filesystem rw as ext2