linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Wols Lists <antlists@youngman.org.uk>,
	opensuse@opensuse.org, linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [opensuse] raid device mounting problem in Leap 42.2
Date: Fri, 14 Jul 2017 11:40:01 +1000	[thread overview]
Message-ID: <87r2xj23v2.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <5967FFAD.6030807@youngman.org.uk>

[-- Attachment #1: Type: text/plain, Size: 2231 bytes --]

On Fri, Jul 14 2017, Wols Lists wrote:

> On 13/07/17 23:46, Istvan Gabor wrote:
>> On Wed, 12 Jul 2017 17:05:17 +0300, Andrei Borzenkov wrote:
>>> On Wed, Jul 12, 2017 at 4:49 PM, Wols Lists <antlists@youngman.org.uk>
>>> wrote:
>>>>
>>>> But I suspect that going back into 12.2, and shrinking the filesystem
>>>> (MAKE SURE you shrink the md device, not the sd device)
>>>
>>> Quite the opposite. Attempting to shrink filesystem that is already
>>> effectively corrupted is potentially dangerous. So the right thing
>>> here is to stop md, backup superblocks (in case they will be
>> 
>> I am puzzled. Do I need to backup the raid superblock or the device
>> superblocks or all?

You cannot have too many backups.

>>                      How do I backup the superblock? I googled but only

mdadm --dump=/some/directory list of devices.

>> find how to recover from superblock backup.
>> 
> The best bet is to ask the linux-raid list what to do.
>
> For the raid list, this is the array I mentioned where the filesystem,
> and the partitions the raid was on, were the same size.

To the byte?  I really like to see the output of commands that report
sizes, rather than have someone claim "were the same size".  It isn't
that I don't trust you.  I just don't trust humans in general (myself included).

NeilBrown

>
> So we have a v1.0 mirror where the filesystem on the mirror uses up ALL
> the space on the md device, not just the free space that it's supposed
> to use, with all the issues that brings like filling up the filesystem
> will overwrite the superblock.
>
> So what's the best way to recover? Will just shrinking the filesystem
> bring everything back the way it should be, or are we better just
> mounting the original filesystem from one disk as if it weren't a
> mirror, and then recreating the mirror on the other disk, copying the
> data, and then adding the first disk back in to put everything back the
> way it should have been?
>
> Cheers,
> Wol
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-07-14  1:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a7cc2751c4c0b89dee040c1522590fb5@gmail.hu>
     [not found] ` <ok4bkp$gb0$1@saturn.local.net>
     [not found]   ` <41e64fb5b9e54bf18aff2d663d0649d8@gmail.hu>
     [not found]     ` <CAA91j0UND1UmwOc46G+o1Mh3dKMG9M_HiYxFdXwWO03D=EztpA@mail.gmail.com>
     [not found]       ` <76df60214c0039114ba0a4b6f0f515bc@gmail.hu>
     [not found]         ` <CAA91j0WXkBnSa+F7u95SWMCtR6nYnUN3uzRLj9jqPoCFX2LNXQ@mail.gmail.com>
     [not found]           ` <596628E7.8020905@youngman.org.uk>
     [not found]             ` <CAA91j0Uyz2xZkpo3YDrkQRhYt5FoG4b-Bwhc7HF3ko40i1xs3A@mail.gmail.com>
     [not found]               ` <d71443c0d631c80af4d09c6098b85359@gmail.hu>
2017-07-13 23:18                 ` [opensuse] raid device mounting problem in Leap 42.2 Wols Lists
2017-07-14  1:40                   ` NeilBrown [this message]
     [not found]                     ` <6df95e9a-1281-ccc6-0d40-7962d8f42bc5@suddenlinkmail.com>
2017-07-14  5:35                       ` NeilBrown

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=87r2xj23v2.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=opensuse@opensuse.org \
    /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).