search for: journal_dev

Newer versions of e2fsprogs refuse modifying journal devices, causing the test #1 of get_e2uuid to fail with: libguestfs: error: set_e2uuid: Cannot modify a journal device. Since the test case just needs to verify get_e2uuid runs without failing, run it without expecting a certain UUID set earlier. Followup of commit da4812ab6b44c29cb3cf181c7aa896420ecb8aa6. --- generator/actions.ml | 15

I am new to ext3 + external journal. Is there any howto I can look at? this is what I understand 1. mke2fs -O journal_dev /dev/md5 2. mke2fs -J device=/dev/md5 /dev/md0 3. mount /dev/md0 / -t ext3 ( hmm.. what do I need to put on fstab?? ) /dev/md5 is a two drive RAID 1 partition /dev/md0 is a 4 drive RAID 5 partition. questions: 1. I am running RedHat 9.0. what extra software I need to use? do I need to patch...

I'm trying to setup an external journal device, but it won't mount as ext3. I can only mount it as ext2. Everything seems happy when I run the commands. It will work when I don't use the external device. This is on RH7.2, linux-2.4.18-rc2. [root@dhcp4 root]# mke2fs -O journal_dev /dev/hdb5 [root@dhcp4 root]# mke2fs -j -J device=/dev/hdb5 /dev/hdb6 [root@dhcp4 root]# mount -t ext3 /dev/hdb6 /home mount: wrong fs type, bad option, bad superblock on /dev/hdb6, or too many mounted file systems [root@dhcp4 root]# mount /dev/hdb6 /home [root@dhcp4 root]# ls /home lost+fo...

...e just installed CentOS 5 on my home box and I want to put the journal on another drive. I created a software RAID-1 device, /dev/md1, and formatted an ext3 file system on it. Now I want to move the journal to /dev/hda5. I've googled for this and the process appears to be: mkfs.ext3 -b 4096 -O journal_dev /dev/hda5 mkfs.ext3 -b 4096 -J device=/dev/hda5 /dev/md1 Now, here's the fun part. I've already put data on /dev/md1. Will the above commands reformat /dev/md1? If so, is there an easy way to move the journal for /dev/md1 to a new partition? TIA! Jeff

...and it seems to be accessible ( we can dumpe2fs and see filesystem information). Here's the system information and command line used to create the filesystem : SuSE SLES9 2 , kernel 2.6.5 ada718-5:/ # rpm -qa | grep e2fs e2fsprogs-1.36-6.2 ----------------------------------------- mke2fs -O journal_dev /dev/mapper/home_jou_vol_grp-home_jou 400000 mke2fs -E stride=16 -O sparse_super,dir_index -j -J device=/dev/mapper/home_jou_vol_grp-home_jou /dev/mapper/home_vol_grp-home Any ideas? Thanks in advance, -- Franco Bladilo Linux/HPCC Administrator Research Computing Support Group Rice Universi...

.../sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 128:20000:16/512 1566 17 11216 24 9255 43 1872 20 500 1 101 1 ss1,4G,28235,94,38522,28,17222,8,22257,61,40274,10,598.0,1,128:20000:16/512, 1566,17,11216,24,9255,43,1872,20,500,1,101,1 # external log mke2fs -v -s 4096 -O journal_dev /dev/sdb6 mkfs.ext3 -v -j -J device=/dev/sdb6 -O sparse_super -O dir_index -R stride=8 /dev/sda1 mount -t ext3 /dev/sda1 /mnt mkdir -m 777 /mnt/t bonnie++ -u nobody:nobody -d /mnt/t -s 4g -m ss1 -n128:20000:16:512 Version 1.03 ------Sequential Output------ --Sequential Input- --Random-...

Hello Is it possible to externalize the journal of an already existing (journal inside) ext3 FS ? Here's what I did to create a new FS with external journal for /dev/emcpowerl2 on /dev/emcpowerl2 mke2fs -O journal_dev /dev/sda10 mke2fs -J device=/dev/sda10 /dev/emcpowerl2 it works perfectly , but can I do the same whitout reformating the original FS; /dev/emcpowerl1 which is in production for exemple thanks.

...journal) + strncat (features, ",has_journal", 12); + else + strncat (features, ",^has_journal", 13); + } + } + if (optargs_bitmask & GUESTFS_MKE2FS_JOURNALDEV_BITMASK) { + if (feature == 0) { + if (journaldev) + strncat (features, "journal_dev", 11); + else + strncat (features, "^journal_dev", 12); + feature++; + } else { + if (journaldev) + strncat (features, ",journal_dev", 12); + else + strncat (features, ",^journal_dev", 13); + } + } + if (optargs_bit...

More comprehensive support for virtio-scsi. Passes all the tests. Rich.

Hello! I have some questions about external journals. On a 4 disk software RAID 5 I have two big devices (one 60 GB, one 180 GB). I would like to give each an external journal on a 2 disk software RAID 1 device and use data=journal. The journal will get its own partition with mke2fs -O journal_dev /dev/mdwhatever. The used 6 harddrives are all IDE drives, they are connected through mainboard and additional ide controllers, each one as master (no slaves). My questions: How big should each of the journals be? Can I put both journals in one RAID 1 device (i.e. give both the same device=/...

...ternal journal (on /dev/md21) to /etc/fstab in order to have it mounted while system-startup. Do I have to specify the external journal device in fstab or does the partition find its journal device by itself? If the first, ho should I specify it? I created the journal with mke2fs /dev/md22 -O journal_dev and the ext3 filesystem with mke2fs -j /dev/md12 -J device=/dev/md22. Thanks again, Norman Schmidt. -- -- Norman Schmidt Universitaet Erlangen-Nuernberg _ cand.chem. Sysadmin Wohnheimnetzwerk RatNET _ // mailto:schmidt@naa.net...

Hi. I'm using e2fsprogs 1.23 on a Roswell system with a patched 2.4.7 kernel (using patch ext3-2.4-0.9.5-247) and am trying to create an ext3 filesystem whose journal is located on another device. The incantation I'm trying is: mke2fs -j -J device=/dev/hdc2 /dev/hdc3 I keep getting an error along the lines of "mke2fs: Journal superblock not found". I've tried creating

...G (argv, i, "-f"); if (correct) @@ -319,7 +326,7 @@ do_mke2journal (int blocksize, const char *device) snprintf (blocksize_s, sizeof blocksize_s, "%d", blocksize); r = command (NULL, &err, - "mke2fs", "-F", "-O", "journal_dev", "-b", blocksize_s, + str_mke2fs, "-F", "-O", "journal_dev", "-b", blocksize_s, device, NULL); if (r == -1) { reply_with_error ("%s", err); @@ -347,7 +354,7 @@ do_mke2journal_L (int blocksize, co...

...og[] = "mke2fs"; - if (e2prog (prog) == -1) + if (e2prog (str_mke2fs) == -1) return -1; char blocksize_s[32]; snprintf (blocksize_s, sizeof blocksize_s, "%d", blocksize); r = command (NULL, &err, - prog, "-F", "-O", "journal_dev", "-b", blocksize_s, + str_mke2fs, "-F", "-O", "journal_dev", "-b", blocksize_s, device, NULL); if (r == -1) { reply_with_error ("%s", err); @@ -395,8 +395,7 @@ do_mke2journal_L (int blocksize, co...

..._ARG (argv, i, "e2fsck"); ADD_ARG (argv, i, "-f"); if (correct) @@ -425,7 +417,7 @@ do_mke2journal (int blocksize, const char *device) wipe_device_before_mkfs (device); r = command (NULL, &err, - str_mke2fs, "-F", "-O", "journal_dev", "-b", blocksize_s, + "mke2fs", "-F", "-O", "journal_dev", "-b", blocksize_s, device, NULL); if (r == -1) { reply_with_error ("%s", err); @@ -453,7 +445,7 @@ do_mke2journal_L (int block...

..._ARG (argv, i, "e2fsck"); ADD_ARG (argv, i, "-f"); if (correct) @@ -425,7 +420,7 @@ do_mke2journal (int blocksize, const char *device) wipe_device_before_mkfs (device); r = command (NULL, &err, - str_mke2fs, "-F", "-O", "journal_dev", "-b", blocksize_s, + "mke2fs", "-F", "-O", "journal_dev", "-b", blocksize_s, device, NULL); if (r == -1) { reply_with_error ("%s", err); @@ -453,7 +448,7 @@ do_mke2journal_L (int block...

Today, I had to uncleanly shutdown one of our machines due to an error in 2.6.28.3. Durin the boot sequence, the ext4 partition /home experienced a journal replay. /home looks like this: /dev/mapper/volg1-logv1 on /home type ext4 (rw,noexec,nodev,noatime,errors=remount-ro) Filesystem Size Used Avail Use% Mounted on /dev/mapper/volg1-logv1 2,4T 1,4T 1022G 58% /home Filesystem

This is a simpler patch that removes GUESTFSD_EXT_CMD completely.

Replace GUESTFSD_EXT_CMD with a command line option ‘./guestfsd --print-external-commands’

Split up the huge generator/actions.ml into several smaller files. Rich.