similar to: ext3 resize failed, data loss

On Fri, May 06, 2016 at 06:19:35PM +0000, Wes James wrote: > 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

This is CentOS-6x. I have cloned the HDD of a CentOS-6 system. I booted a host with that drive and received the following error: checking filesystems /dev/mapper/vg_voinet01-lv_root: clean, 128491/4096000 files, 1554114/16304000 blocks /dev/sda1: clean, 47/120016 files, 80115/512000 blocks /dev/mapper/vg_voinet01-lv_home: clean, 7429/204800 files, 90039/819200 blocks

Hello, First off, I'm not sure if my problem is with my filesystem, or with my partition table, so this may or may not be the appropriate list for this question - if not, I'd appreciate being pointed to a more appropriate forum. My problem is that when trying to resize, copy or move my ext3 partition in parted, I get the following error: No Implementaion: this ext2 filesystem has a rather

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

Simon May <simon@imsl.es> wrote: > We use kernel 2.4.18 with a slackware linux dist. > e2fsprogs version 1.29 > > you will see that sendmail was the application that lead to the error > at the time the machine was doing a weekly new letter to clients > which puts it under abit of load but not a lot really > the machine has a 1 Gb processor and 768 Mb RAM so is

> > From: Scott Robbins <scottro11 at gmail.com> > Date: May 06, 2016 12:32:55 PM > To: CentOS mailing list <centos at centos.org> > Subject: Re: [CentOS] resize lvm > > On Fri, May 06, 2016 at 06:19:35PM +0000, Wes James wrote: > > 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

Hi! I have made some extensions to debugfs to undelete or recover files from a damaged ext3 file system. Salvage or undelete files of damaged ext2/ext3 file systems debugfs salvage command can be used to salvage files from a damaged ext3 or ext2 file system. The code is alpha, so use at your own risk. the usage is: salvage first-block count-blocks Salvage tries to salvage files found in

Hi folks, Is it possible to resize an ext3 filesystem while it's online? It looks like resize2fs won't do the trick unless the filesystem is unmounted. And ext2resize takes one look at the filesystem while it's mounted and complains as well, this time about un-supported features. It's not a huge deal if I have to shutdown the system to grow the two filesystems, it's just

Hi there, For years I've been using the ext3 file system without to think that it can ever gets broken so bad. This was until last week when a box that I have running Linux from a SanDisk CF went down. Since then I am struggling with this CF trying to understand what is happening. The CF is SanDisk ultra II 1GB. On this I have 4 partitions all of them with ext3: boot / swap

Rebooting to try 2.4.7-ac4, I had Xfree86 crash on exit and hang the machine (it does that once a month or so; this notebook gets booted quite often). After fscking the root and another ext2 partition, the system got to the big ext3 partition and just went dead. No message, no disk activity, no keyboard response. I powered down and rebooted 2.4.7-ac3 patched with ext3-2.4-0.9.5-247ac3, and that

Hi Andreas, Any plans to do a release of the online resizing patch for ext3-1.0? I've put off asking about this until Al Viro's superblock handling and other fixes were done, but now that LVM 1.0.1 seems to be approaching a stable and -linus/-ac mergeable state, this would certainly make deploying ext3+LVM a lot simpler. Regards, Bill Rugolsky

On 09/20/2014 12:07 AM, Andreas Dilger wrote: > On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008@gmail.com> wrote: >> I am reporting this on the advice of the Fedora Users Mailing List Member. >> >> This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. >> >> I am reporting this per

Hi Everyone, I have a server which has a raid array on /dev/sdb. After a crash I tried to mount the array and it failed with: mount: wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or other error dmesg reports: EXT3-fs: invalid journal inode. I tried to run e2fsck and it failed (The output can be seen below). If anyone has any suggestions on how I can restore

Hello. We have, over the last few months, lost ext3 filesystems three times. The whole filesystem left unusable. nfs-server:~# mount /dev/rd/c0d1p1 /mnt -t ext3 mount: wrong fs type, bad option, bad superblock on /dev/rd/c0d1p1, or too many mounted file systems (in dmesg) EXT3-fs: journal inode is deleted. EXT3-fs: get root inode failed nfs-server:~# fsck /dev/rd/c0d1p1 Parallelizing

Hi everyone, I've been running Redhat 7.2 (new install) for about 2 weeks now without any problems, but today I was not so lucky. My system hung while I was trying to configure the kernel-source RPM using 'xconfig'. After rebooting the system, it seems that my whole ext3 file system is corrupted. I get the message: Mounting root filesystem EXT3-fs: ide0(3,3):couldn't mount

Hello there, I'm a new to linux need help in regards to issues during mounting of a new created logical unit which I am unable to mount the volume due to error as found below: ~]# mount -l -t ext3 /dev/mapper/vgNebula-lvg1 /mnt/iscsi0 mount: wrong fs type, bad option, bad superblock on /dev/mapper/vgNebula-lvg1, missing codepage or helper program, or other error In some cases

Hi everybody! I'm using LVM and ext3 and am very satisfied with it. But now I have the following problem: I have a filesystem on a LV which is in use - files are created, modified and so on. To do a backup I'd like to create a snapshot of this volume which gets backup'd and then dropped. # lvcreate -s -L 20M -n snapshot /dev/vg/data lvcreate -- WARNING: the snapshot will be

Hi, hoping that someone on this list can help me here is the Problem. After a crash it seems the journal could not be recovered. This is what mount gives: root@wuehlkiste:# mount -t ext3 /dev/hdb2 /mnt mount: wrong fs type, bad option, bad superblock on /dev/hdb2, or too many mounted file systems and this is the corresponding logfile-entry: Nov 27 11:16:13 wuehlkiste kernel: attempt to

hello. had a bad day yesterday: accidentally, the first 0.5% to 1% of my ext3 partition got overwritten, can't gauge it more exactly. Geography of the partition is: size ~100 GB. block size should be 4096. => deleted are averages to 500mb - 1gb still. I don't think it is relevant, but the device itself is /dev/loop0, because there is a cryptoloop layer between the device and the