linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Marc des Garets <marc@ttux.net>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] broken fs after removing disk from group
Date: Fri, 14 Nov 2014 20:30:58 +0100	[thread overview]
Message-ID: <54665872.2020101@ttux.net> (raw)
In-Reply-To: <54665506.3070301@ttux.net>

I am in luck, I rebooted and fsck no longer complains about the size of 
the physical blocks that differ from the filesystem so now it's running 
and I believe it should be successful. I expected the reboot would sort 
this out after I saw the lvdisplay was giving the right size but that 
fdisk -l was not. I can still mount my partition and access the files so 
now I expect fsck to get rid of the files that were on the dead disk and 
which are now obviously giving I/O errors.

On 11/14/2014 08:16 PM, Marc des Garets wrote:
> I got a lot back from this file system. I only lost what was on that 
> dead disk and by chance there weren't much data on it, most is on the 
> other 2. I already know what I lost, I was lucky and it's not very 
> important: some GC heap dumps and some backup of phone sd card.
>
> I made a backup of what was important now and so I'll be trying fsck. 
> I hope it will work because I don't feel like rebuilding my lvm and 
> copy everything again and lose what I consider not important.
>
> Thanks.
>
> On 11/14/2014 06:12 PM, Jack Waterworth wrote:
>> If you get anything back from this file-system I would be impressed. 
>> Losing 200GB of a file-system isnt something small that can just be 
>> "made up" to restore the data. The only options I can think of would 
>> be to (1) restore from backup, (2) copy as much data as you can off 
>> onto a new location, (3) fsck.    #1 is probably the best in your 
>> situation, however if that's not an option you should try to save as 
>> much data as possible (#2).
>>
>> a fsck should be able to repair the file-system back into a "good" 
>> state, but you'll likely lose a lot of data. Can you show us the full 
>> error output you're getting when you try to fsck?
>>
>> Also, keep in mind that this is an LVM mailing list... not a 
>> filesystem one. Perhaps you could get some help in #ext4 on the OFTC 
>> IRC.
>>
>>   Jack
>>
>> On 11/14/2014 03:42 AM, Marc des Garets wrote:
>>> ext2fs_open2: The ext2 superblock is corrupt 
>>
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-lvm
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>

  reply	other threads:[~2014-11-14 19:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12 22:16 [linux-lvm] broken fs after removing disk from group Marc des Garets
2014-11-12 23:11 ` Fran Garcia
2014-11-13  7:21   ` Marc des Garets
2014-11-13  9:47     ` Marc des Garets
2014-11-13 19:27   ` Marc des Garets
2014-11-13 19:48     ` matthew patton
2014-11-13 20:04       ` Marc des Garets
2014-11-14  8:42         ` Marc des Garets
2014-11-14 17:12           ` Jack Waterworth
2014-11-14 19:16             ` Marc des Garets
2014-11-14 19:30               ` Marc des Garets [this message]
2014-11-14 20:54                 ` Marc des Garets

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54665872.2020101@ttux.net \
    --to=marc@ttux.net \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).