similar to: repeated crashes

I am using SuSE 7.3 compiled ext3 support into the kernel and installed it. All my partitions load up as ext3 except / . I ran tune2fs several times, still doesn't take on the / drive. Most recent dumpe2fs -h show no features on that drive=, I keep going around in circles, removing .journal from / and running tune2fs but it never works for / What am I doing wrong? ( thanks in advance)

Hello everybody, I''m playing with Xen and trying to extend DomU disk space. My Configuration: Dom0: all Xen machine are HVM. They''re installed on LVM. I''ve one VG (XEN) on Dom0 and created a LV (here, xps.101.disk) per DomU. disk configuration in xen conf is as follow: disk = [ ''phy:/dev/XEN/xps.%d.disk,ioemu:hda,w'' % (vmid)

Hi, I tried to convert my root partition from an ext2 to ext3 fs using tune2fs. I'm running a 2.4.10 kernel with ext3 support, but the partition is not mounted ext3. In fact the journal feature is missing from the superblock: # cat /proc/filesystems | grep ext ext3 ext2 # tune2fs -l /dev/hda6 | grep features Filesystem features: filetype sparse_super # ls -l /.journal

Hi, I was trying to run a guest OS with multiple partitions. I added a line like disk=[''phy:hda6,hda6,w''] in the configuration file. The disk was not mounted in the host OS. However, the kernel refuses to boot with an error message which says "kernel not syncing... attempted to kill init... rebooting...". When I remove that line, everything works. Is there

Here I don't want to start a discussion, but rather share a *solution* that took me some days to come up with. The whole stuff started with a power-outage. After reboot, my server (ext3) came back with the dreaded file system error (Ctrl-D to reboot or password for maintenance) - if you've never seen this, consider yourself lucky! In any case, I did the fsck as prescribed, but abandoned

I often get the message: EXT2-fs warning (device hda6): ext2_fill_super: mounting ext3 filesystem as ext2 I have googled for a reason and a way to solve this - but not found something I could use. Maybe somebody here konws what to do? best regards keld

Suse 10.1 AMD64 Xen3 New to Xen. The dom0 is up and running. I am trying to get my first domU working. My approach is to use precompiled images from jailtime.org. After some manual tinkering with the .cfg file the domU proceeds to boot but stalls with the following error. I cannot get past this - any ideas ? Brian Using config file "/etc/xen/vm/vm1". Started domain vm1 Bootdata ok

Hi I got a strange error, happening on two of my ext3 partitions. What can be wrong? And why does e2fsck error out, instead of displaying an error message? Best regards keld fsck /dev/hda6 fsck 1.38 (30-Jun-2005) e2fsck 1.38 (30-Jun-2005) Warning... fsck.ext3 for device /dev/hda6 exited with signal 11. also From my dmesg: <1>general protection fault: e7a8 [#3] Modules linked in:

Background: This is a dual boot (Windows XP and CentOS 5.2 (32 bit) box. There were four (4) NTFS partitions. The C partition got full. I deleted the 4 NTFS partitions and did a clean install of Windows XP, into one (1) NTFS partition. I knew that I would need to install GRUB again and I did that, using the CentOS 5 Installation DVD. When I tried to boot into Linux, no joy. this is the GRUB error

I posted this to the Fedora-test list but I''ll try here. If I need to ditch fedora rpms and move to building directly from src before posting here, please let me know and I''ll do so (apologies in advance if this is the case). I have the following Fedora RPMS installed: kernel-xen0-2.6.10-1.1155_FC4 kernel-xenU-2.6.10-1.1155_FC4 xen-2-20050222 I can

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

Hi, I have installed Red Hat Linux 7.3 with ext2 file system and I have multiple partition. I converted them to ext3 using following command. tune2fs -j -i 0 /dev/hdaX And I modified /etc/fstab as below. LABEL=/ / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts

Hi, i am having problems converting the rootfs - I created a journal and booted with "rw rootflags=journal=<inode>" - Before i changes the fstab and put the WIP fsck to /sbin/fsck.ext3. The kernel seems to mount the filesystem ok and then the bootup scripts (debian potato) try to fsck the rootfs which leads to e2fsck 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 JFS DEBUG:

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 have patched the kernel and recompiled the kernel with the ext3 support, however, when i boot up, i get this error below, what have i missed ? request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device "hda6" or 03:06 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 03:06

Im intending use Ext3 file system in my web farm. Im using RedHat 6.2 (kernel 2.2.16-3) and Turbo Linux Cluster Server 6.0. I have NO SUCCESS in path my own kernel. I downloaded the following ext3 packages: ext3-0.0.2f.tar.gz (linux-2.2.16-3.kdb.diff , linux-2.2.16-3.ext3.diff ) e2fsprogs-1.20-0.WIP.i386.rpm e2fsprogs-1.20-0.WIP.src.rpm e2fsprogs-1.20-0ext3.i386.rpm

HI, I am trying to find out why an old slower machineis faster than a new faster machine. I have a RedHat 6.2 server installation, it runs samba and I have been very happy with it. Filesystem is:- [darryl@keg darryl]$ df -h Filesystem Size Used Avail Use% Mounted on /dev/hda6 1.2G 735M 387M 66% / /dev/hda1 40M 3.0M 35M 8% /boot /dev/hdc1

Which disk is it? /dev/sda6 or /dev/sdb8 or /dev/sdc6? >From my log: Jun 10 21:25:39 postamt1 kernel: attempt to access beyond end of device Jun 10 21:25:39 postamt1 kernel: 08:06: rw=0, want=1680353324, limit=59954548 Jun 10 21:25:39 postamt1 kernel: EXT3-fs error (device sd(8,6)): ext3_readdir: directory #3473659 contains a hole at offset 1852399616 $ mount /dev/sdb6 on / type auto (rw)

Hi, my / is located on /dev/hda6 and my "personal storage partition" - the palce where I store my important files - is located on /dev/hda9. I've deleted a couple of files in /dev/hda9/xyz/abc. Exactly I've deleted the whole directory "abc" with mc. Now hda9 is unmounted, of course. Can you give me a recipe about how to recover those files, please! Probably

I get the following warning when running xend start, and a similar warning sometimes when doing xm commands: /usr/lib/python/xen/xend/XendNode.py:26: RuntimeWarning: Python C API version mismatch for module xen.lowlevel.xc: This Python has API version 1012, module xen.lowlevel.xc has version 1011. import xen.lowlevel.xc /usr/lib/python/xen/xend/xenstore/xstransact.py:10: RuntimeWarning: