similar to: resizing an ext3 partition

I tried it on loop. 1. mount /dev/loop0 /mnt/test -t ext3 2. cp files to 100% full 3. umount /mnt/test 4. fsck.ext3 -f /dev/loop0 Inode xxxxx, i_blocks is xxx, should be yyy. Fix?

Hi, We have recently switched from XFS to ext3 do to various corruption scenarios that were witnessed. Does ext3 have something like xfs_growfs for growing the FS to the end of the underlying partition? Thanks, Menny

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Does anybody have any links/howtos on creating an encrypted file system using ext3? Basically I want to encrypt /home and be asked the password when I mount the file system. - -- Cheers, Chris Howells -- chris@chrishowells.co.uk, howells@kde.org Web: http://chrishowells.co.uk, PGP key: http://chrishowells.co.uk/pgp.txt KDE:

Hi, I get the error "Operation not permitted" when I try to delete a file as root, see some commands below. - there is no "i" attribute - it's a problem with the files and not the upper directories since I can delete a similar file in the same directory - fsck -f doesn't find any error on the partition - the partition is mounted rw If this is not the right place to

I accidentally removed an ext3 partition from the partition table. I know roughly where it started. Is there any way of finding the superblock and reconstructing it? TIA, Dave (Yes I have a backup of the important stuff!)

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:

Hi, I try to convert my RedHat 7.3. partitions from ext3 to ext2. I have found a thread dealing with this issue. Thus: "tune2fs -O ^has_journal /dev/foo" and "e2fsck /dev/foo" will do the magic! This works fine for "/boot" but when I try to convert "/" my kernel panics? The kernel panics message appears shortly after the attempt to startup kjournald. How

i have a question on ext3 modes and am not sure if this list is still active

I've been running RH 72 on my Dell at work. Since I use more than one system and I test things, I forgot that I had the root partition as ext3. That machine has two kernels on it. One is the stock 2.4.7 RH 72 and the other is the new 2.4.17 that I compiled last week. This morning I logged in and typed startx. The kernel responed by coughing up a lung and segfaulted. Couldn't run any

Hello, I am using Xen 4.0.1 and Xen 3.2.1 dom0 with Debian Lenny and Squeeze dom0s. I have a bunch of virtual machines running , all using LVM as backend storage. Mostly, an LVM logical volume is mapped to a partition in the VM (eg: xvda1) I have tried to hot resize the filesystem in the VM without umounting it but it just do not work... Here is what I did: - lvextend on the dom0, -

Hello Mailing List! A quick question. Has anyone gotten a resize (in my case grown) a Xen DomU disk image? Here is the procedure I have followed: 1. Install a DomU using virt-install Customize xvda to be all one partition ext3 2. On Dom0: dd if=/dev/zero bs=1G count=1 >> <my_disk_image> ll -h (Image is now 1GB larger) xm create <DomU> On DomU: df -h (Size has not

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)

Greetings - I had a logical volume that was running out of space on a virtual machine. I successfully expanded the LV using lvextend, and lvdisplay shows that it has been expanded. Then I went to expand the filesystem to fill the new space (# resize2fs -p /dev/vde1) and I get the results that the filesystem is already xx blocks long, nothing to do. If I do a # df -h, I can see that the

Hi all, I want to setup a linux workstation with FC4 and with all the partitions (except for /boot) under LVM to be able to resize them in future. I don't need online resizing, I can shutdown the system and reboot with the rescuecd when needed. I have done some test on this configuration and I have sverals doubts: If i format a partition with the resize_inode feature enabled and I resize it

I have a file system I am trying to resize via resize2fs but I get this error resize2fs 1.41.14 (22-Dec-2010) resize2fs: New size too large to be expressed in 32 bits im on debian squeeze 2.6.32-5-amd64 # pvs ? PV???????? VG????? Fmt? Attr PSize? PFree ? /dev/md1?? vgRAID6 lvm2 a-?? 18.17t 134.12g # lvs ? LV??? VG????? Attr?? LSize? Origin Snap%? Move Log Copy%? Convert ? data1 vgRAID6 -wi-ao

steps to reproduce: ./run guestfish -N disk:1536M <<EOF part-init /dev/sda mbr part-add /dev/sda p 1 1048577 part-add /dev/sda p 1048578 2097154 part-add /dev/sda p 2097155 -1 mkfs ext2 /dev/sda1 mkfs ext2 /dev/sda2 mkfs ext2 /dev/sda3 EOF qemu-img create -f raw test2.img 1520M ./run virt-resize --format raw --output-format raw --resize /dev/sda1=-2M --resize /dev/sda2=-8M --shrink

I have a laptop that I put centos 7 on and I started out with a 30gig partition.? I resized the other part of the disk to allow more space for centos.? I then created an unformated partition in the available space,? ran pvcreate /dev/sda4 vgextend lvname /dev/sda4 lvextend -L 184.46G /dev/lvname/root but when I run: sudo resize2fs /dev/lvname/root I get: resize2fs: Bad magic

On May 06, 2016, at 12:29 PM, John R Pierce <pierce at hogranch.com> wrote: On 5/6/2016 11:19 AM, Wes James wrote: sudo resize2fs /dev/lvname/root I get: resize2fs: Bad magic number in super-block while trying to open /dev/lvname/root Couldn't find valid filesystem superblock. what file system type is this /dev/lvname/root ? I tried to find the type from blkid /dev/sda4

Hi, I'm about to roll out a whole bunch of Redhat Enterprise 4 workstations and have run into problems cloning from the original. Normally I would use ghost (v7.5) because it does a nice job when cloning to a different sized disk.Unfortunately it comes up with read error 29004. Looking around it seems that Symantec don't support Fedora Core 3 (with Ghost v.8 - don't know if v.9 works

Hello everyone! I am working on resizing qcow2 images using virt-resize+liguestfs. E.g. I when shrinking a partition, I have to resize filesystem using resize2fs-size. The problem is that I cannot find out minimal partition size (aka resize2fs -P). The only way is calling "resize2fs-size 1K", wait for resize2fs to claim "resize2fs: New size smaller than minimum (510050)"