search for: e2fsk

On Tue, 26 Jul 2016 16:21:00 +0100 (BST) John Hodrien <J.H.Hodrien at leeds.ac.uk> wrote: > On Tue, 26 Jul 2016, Gabriele Pohl wrote: > > > on all of my CentOS7 VMs on different hypervisors > > the config file e2fsck.conf contains the line > > > > broken_system_clock = 1 > > > > Do you see similiar /default/ settings on > > your machines? Is

...ohl wrote: > > I now changed the value to 0 and rebooted. > > > > After that fsck based on Interval setting were done. > > > > Unfortunately that is not true for the root partition. > > For that I had to use maxCount settings to trigger fsck. > > I believe e2fsk happens both pre root mount, and post. You'll want to > rebuild your initramfs to make it take effect for the root volume I'd guess. agreed as I see the config is included there: # lsinitrd | grep e2fsck -rw-r--r-- 1 root root 112 Mar 5 2015 etc/e2fsck.conf -rwxr-xr-x...

...voinet01-lv_log The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsk -b 8193 <device> /dev/mapper/vg_voinet-lv_spool: clean, 372/614400 files, 171186/2457600 blocks *** An error occurred during the file system check. *** Dropping you to a shell; the system will reboot *** when you leave the shell. Give root password for maintenance (or type Control-D to cont...

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

...d -L 184.46G /dev/lvname/root I find it easiest to do lvextend -l 100%VG /dev/lvname/rootI find it easiest to do lvextend -l 100%VG /dev/lvname/root. (Then, if practical, and since it's a laptop, I'm guessing it's not a production machine), reboot from a livecd or whatever and doing e2fsk -f /dev/lvmname/root I don't know if it will solve your issue, but may be worth trying. > > > but when I run: > > > > sudo resize2fs /dev/lvname/root > > > I get: > > > > resize2fs: Bad magic number in super-block while trying to open /dev/...

...gt; > > > I find it easiest to do lvextend -l 100%VG /dev/lvname/rootI find it > easiest to do lvextend -l 100%VG /dev/lvname/root. > (Then, if practical, and since it's a laptop, I'm guessing it's not a > production machine), reboot from a livecd or whatever and doing e2fsk -f > /dev/lvmname/root > > I don't know if it will solve your issue, but may be worth trying. I found this: # lvextend -l +100%FREE /dev/myvg/testlv doing a search. What's the difference between 100%VG and 100%FREE? Thanks, -wes

...nks for the hint :) > > I now changed the value to 0 and rebooted. > > After that fsck based on Interval setting were done. > > Unfortunately that is not true for the root partition. > For that I had to use maxCount settings to trigger fsck. > > fyi and cheers, I believe e2fsk happens both pre root mount, and post. You'll want to rebuild your initramfs to make it take effect for the root volume I'd guess. jh

...my filesystem. The fs is now the right size and mounts fine, but everything just got dumped into lost+found. Is there any way I can fix this and get my data back? At least get it back to its previous state so I can mount it ro and copy my data off? Is my old superblock backed up somewhere, or does e2fsk update the backup superblock as well? Would my old superblock even help, or did the fsck trash my inode structure? Currently I think I have all my data, just dumped in lost+found without filenames - is there any way to salvage anything from that? And is this a known bug in ext2resize? In parted?...