linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Jack Waterworth <jack@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] broken fs after removing disk from group
Date: Fri, 14 Nov 2014 12:12:10 -0500	[thread overview]
Message-ID: <546637EA.1010203@redhat.com> (raw)
In-Reply-To: <5465C07A.2080707@ttux.net>

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 

  reply	other threads:[~2014-11-14 17:12 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 [this message]
2014-11-14 19:16             ` Marc des Garets
2014-11-14 19:30               ` Marc des Garets
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=546637EA.1010203@redhat.com \
    --to=jack@redhat.com \
    --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).