similar to: Question about Journaling Root Filesystem.

I am trying to use data=journal for my root file system. If I add: Kernel /vmlinuz-2.4.7-10 ro root=/dev/hda2 rootflags=data=journal To my grub.conf file, all I get is a kernel Panic, "EXT2-fs: Unrecognized mount option data. Kernel panic: VFS unable to mount root fs on 01:00" My fstab file is: LABEL=/ / ext3 defaults 1 1 Any suggestions?

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, "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 thought I've found three bugs on syslinux 6.03: (1) With sample config file as is, i.e. leaving commented MENU VSHIFT and MENU COLOR UNSEL but uncommented MENU COLOR SEL: A black "border" is displayed below the selected line and on its right edge. (2) Uncommenting MENU COLOR UNSEL: This effect appears also on separators and on right edge on every unselected lines. (3)

EXT3 developers: I am curious, if EXT3 is currently being used on the root partition in "data=ordered" mode (the default as I understand), and I want to have the it come up in data=journal mode, how do you effectuate this conversion? I would also be curious how to know if anything special is required for doing so for the /boot partition as well. I believe that with the /home partition,

Hello LINUX GURUS, I am fairly new to LINUX OS, so pardon my ignorance about LINUX OS. I have installed LINUX 7.2 on IBM netfinity 4000R server. OS works fine for few days and start giving me this error message all of a sudden: "kernel: hda: dma_intr: status=0x51 { Driveready SeekComplete Error }" "kernel: hda: dma_intr: status=0x40 { UncorrectableError }, LBAsect=4944861,

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:

I am using RedHat 7.2 w/ kernel 2.4.7-10. My / filesystem is configured as ext3. I want to change it to use data=journaled instead of ordered. If I mount it from a boot floppy, it mounts fine. (mount /dev/hda2 /mnt -t ext3 -o data=journal). I have attempted to find the correct procedure to start it up as journaled from grub to no avail. I have created a new initrd image that works fine with

Hi, I'm running 2.4.9-ac7 with ext3 compiled in, and I ran across this problem. Now that I look back, it makes sence, but it wasn't obvious at first... I wanted to change the journal mode on my / partition, so I changed my fstab to: /dev/hda1 / ext3 defaults,errors=remount-ro,data=journal 0 1 as well as several other partitions, and rebooted. After rebooting I had a read only / that I

Hi, Updated to current bk today, and my machine stopped booting ... I''ve tracked it down to the apic changes from end of last week. cset 1.1307 boots fine, 1.1308 doesn''t. Diff of the boot messages is below. Full logs are also attached. Gerd --- log-1.1307 2005-04-21 14:40:57.372885027 +0200 +++ log-1.1308 2005-04-21 14:38:52.236553392 +0200 @@ -7,7 +7,7 @@

I've posted here with this problem before, and while several people DID try to help, nothing seems to work! Here's the situation (again): I have a Linux box (Mandrake 7.0) running Samba (2.0.6) compiled from source. I can mount/read/write the linux shares just fine, but when trying to write to my Win98 shares (which mount perfectly), I get "permission denied". This only

Doing some debugging of my kernel build with ext3 and noticed something interesting. At the bottom of the rootflags options processing loop there is a return failure if there was an option that ext3 did not know about. Should this be the behaviour? Would it not be better to ignore options not recognized? Surely, some day, some other filesystem is going to want to use rootflags to have one of

Hi, Just got Fedora FC1 vanilla 2.4.25kernel+libata8patch booting problems, FC1 complains that it can not automatically find&found partitions specified with "LABEL=" in /etc/fstab, and then falls me into repair mode. In the repair mode I can mount it manually without any problems. More interesting are: 1) I have several partitions specified with "LABEL=*" in

I doubt that this is actually an ext3 problem so I'm taking a bit of a liberty, but... We have several machines that have two ext3 partitions (/, /boot) and a large raw partition. Something happened that destroyed both the ext3 partitions on all machines. I appears that the app writing to the raw partition had a bug that caused it to write to negative block numbers and that this wrote all

Hi! Is there a way to view ext3 filesystem's maintained journal (in a human-readable-format)? I ask, because i have had a server crash before and now i'm wondering if i might take a look at last things that my server did straight before crash. I guess clarifying log insertions might be lost before buffers were flushed to disk. Thx.

hi all, i have reinstalled linux i kept free 17 gb space. i have created 4gb partition by fdisk with LVM options. fdisk -l Disk /dev/sda: 40.0 GB, 40060403712 bytes 255 heads, 63 sectors/track, 4870 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 1275 10241406 7

hi all, i have reinstalled linux i kept free 17 gb space. i have created 4gb partition by fdisk with LVM options. fdisk -l Disk /dev/sda: 40.0 GB, 40060403712 bytes 255 heads, 63 sectors/track, 4870 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 1275 10241406 7

Hello, What am I missing ? thanks ! -dikshie- @fisbum:/usr/bin$ uname -a Linux fisbum 2.4.18 #3 Tue Mar 19 16:55:23 JAVT 2002 i686 unknown @fisbum:/usr/bin$ mount /dev/hda1 on / type ext3 (rw,errors=remount-ro) /dev/hda3 on /usr type reiserfs (rw) /dev/hda5 on /home type reiserfs (rw,nosuid,usrquota) /dev/hda6 on /var type reiserfs (rw,usrquota) /dev/hda7 on /tmp type reiserfs (rw) /dev/hdb1

Please help me understand why I am unable to connect to and browse the newly configured DFS tree that I installed on my Samba server according to the instructions found in Chapter 18. "Hosting a Microsoft Distributed File System Tree" of the official how-to. Irrespective of whether I try to access the dfs file tree from either the local file browser (and choosing the SMB tree) or from

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)