similar to: Changing journaling mode on root / loop-aes

Dear Sir or Ma'am: I am interested to think about implementing EXT3 onto my servers here. However, I have some concerns and am hoping someone can address them. 1) If I install ext3 what is the likelihood that the extent of damage caused by its bugs will be limited to just the fact that the journals may not work properly? Alternatively, do I risk real damage to files and the filesystem at

Dr. Tweedie, et al.: I have decided to move to EXT3 from ReiserFS if I can get tail packing for EXT3. Last I had asked about it, someone had written some sort of patch but it was not official (I think), and was questionable if it had worked or not. Can someone tell me the status in the instant? If I installed 2.4.18 or a later kernel, would tail packing be part of EXT3? How would I turn it on or

Dr. Tweedie, et al.: I recently formatted a partition using EXT3, and after a "df -h" I get 14GB of space. When I reformatted the partition with ReiserFS, and did a "df -h" I got 16GB of space! Now the partition was setup to be 16GB via fdisk, so 16GB is correct. However, why does EXT3 loose 2GB of space? The journals cannot be that big!?! Very Respectfully, Stuart

Question 2a) I am also working with arules package and I have the following problem let suppose the matrix b like: b<-matrix(c(1,1,1,1,1,1,0,0,1,1,1,1,0,0,1,1,0,1,1,1,1,1,1,1),nrow=6) rownames(b)=c("T1", "T2", "T3", "T4", "T5", "T6") colnames(b)=c("It1", "It2", "It3", "It4") bt<-as(b,

I am trying to use data=journal on my root file system. I have separate slices on which journal=data works fine on all of them, except root. I have tried putting rootflags=journal=data on my kernel line in Grub, but I get a kernel panic. I'm missing something simple, I jut know it. It can't be the kernel version because it works on the other slices. My etc/fstab file is as follows:

Dear sir, I have a matrix like a<-matrix(c(0,2,0,4,0,6,5,8,0),nrow=3) colnames(a)<-c("F1","F2","F3") rownames(a)<-c("A1","A2","A3") a F1 F2 F3 A1 0 4 5 A2 2 0 8 A3 0 6 0 I want to extract all pairs (rownames, columnames) from which the value in the matrix is 0 The result should be something like this A1, F1 A2,

> IT3 Stuart Blake Tener, USNR-R" <stuart@bh90210.net> writes: [...] > I really did not mean to insult anyone, just I like choice too, > and I want to see that choice in RH distributions also. I guess we're just circling around the main issue here: it's great you really like Reiser and think it's k3wl or whatever, but this isn't the place to come tell us about

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

Please be aware that I HAVE NOT TESTED THIS PROGRAM... please try it in a "safe" environment since for all I know it could nuke your "real root" by mistake. -hpa

I tried to convert / to ext3, so I went ahead and entered rootflags=noload,journal=355 on the LILO prompt. The kernel failed to mount /: EXT3-fs error (device ramdisk(1,0)): ext3_get_inode_loc: bad inode number: 355 The boot device is a scsi hard disk, so initrd is used to load the scsi driver, before mounting /. So, it looks like the kernel rootflags= arg gets applied to the ramdisk, not the

Hi all, I was trying to mount root-partition which is ext3 partition with noatime and ro option. I included "ro" in the kernel command line But for mounting it with "noatime" option when I searched for some solution I came across a patch http://lkml.org/lkml/2007/8/5/38 But after applying this patch and including option "noatime" in

My guinea pig laptop has only a / partition, and a small /boot partition. I installed the ext3 kernel succesfully (I think). Now, how do I get / converted to ext3? I'm thinking: * Use mkbootdisk on a floppy, to create a boot disk with the ext3 kernel. * Boot off the floppy. * Follow the instructions to convert / to ext3. * Change the filesystem type in /etc/fstab to ext3. * Reboot.

I hate to bother the list with this, but I am lost. With our servers that use LILO we use append=rootflags=data=journal. I have read everything I can find on GRUB, the key is everything I can find, and I have no idea how perform the same function in grub.conf Randy

On Tue, Feb 24, 2015 at 11:56:50PM +0100, Olivier Mauras wrote: > > > On Tue, 2015-02-24 at 16:05 -0500, Laine Stump wrote: > > On 02/24/2015 03:37 PM, Olivier Mauras wrote: > > >> Hello, > > >> > > >> I've been trying to boot a VM with the rootfs being a 9P share from > > >> the host. The VM OS is centos 7. > > >>

Hi Thomas, >----Messaggio originale---- >Da: thomas@kupper.org >Data: 22/01/2010 10.48 >A: "Leszek Ciesielski"<skolima@gmail.com> >Cc: "linux-btrfs"<linux-btrfs@vger.kernel.org> >Ogg: Re: mount command not honoring rootflags passed > > >On 22 Jan 2010, at 10:40, Leszek Ciesielski wrote: > >> On Fri, Jan 22, 2010 at 10:30 AM,

On Wed, Aug 27, 2014 at 10:34 AM, Christopher Covington <cov at codeaurora.org> wrote: > On 08/27/2014 12:19 PM, Andy Lutomirski wrote: >> On Wed, Aug 27, 2014 at 9:13 AM, Christopher Covington >> <cov at codeaurora.org> wrote: > > Virtme looks interesting. If it's any use, here is my modest QEMU command line > collection. > >

On Wed, Aug 27, 2014 at 10:34 AM, Christopher Covington <cov at codeaurora.org> wrote: > On 08/27/2014 12:19 PM, Andy Lutomirski wrote: >> On Wed, Aug 27, 2014 at 9:13 AM, Christopher Covington >> <cov at codeaurora.org> wrote: > > Virtme looks interesting. If it's any use, here is my modest QEMU command line > collection. > >

Hi I am running a pxe diskless node in f13 and I have some proposals to make ovirt-early working in this version. nash is no more available (nash/mkinitrd is replaced by dracut), so this following command fails : "echo "network --device $DEVICE --bootproto dhcp" | nash" it makes the network configuration incomplete. I replace the linuxrc command by dhclient and it's

Red Hat Software has been notified of a critical security problem (a buffer overrun) in /usr/bin/sperl*. As no official fix for this problem exists, we recommend turning off the setuid bit on /usr/bin/sperl*. As far as we know, this problem affects all platforms and all versions. As soon as a fix is available we will release a new version of the perl package and announce it here. If no fix seems