linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Majed B." <majedb@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: RAID5 / 6 Growth
Date: Sun, 20 Dec 2009 02:59:29 +0300	[thread overview]
Message-ID: <70ed7c3e0912191559i75bdc191p55a93568b18f1652@mail.gmail.com> (raw)
In-Reply-To: <4B2D6447.1070406@anonymous.org.uk>

John,

I grew software RAID arrays with XFS on top without issues before. I
tried with the filesystem both mounted and unmounted. Never had a
problem. And XFS can't be grown unless it's mounted, so the size of
the block device is not the one causing the issue here, as the size of
the block device (array) is larger than what the filesystem is
occupying, which is normal.

After mounting the filesystem, the admin can increase the size of the
FS to fit the newly expanded array size.

On Sun, Dec 20, 2009 at 2:39 AM, John Robinson
<john.robinson@anonymous.org.uk> wrote:
> On 19/12/2009 20:19, Leslie Rhorer wrote:
> [...]
>>>
>>> The reason why you can't mount even though repair suggests you do
>>> might be because of a bug in xfsprogs/libs not a complete corruption
>>> in the filesystem itself.
>>
>>        It's possible, I guess, but the diagnostics seem pretty coherent.
>> Running xfs_repair in test mode finds a small but reasonable number of
>> issues.
>
> Please excuse me if this is a stupid question, but is it possible any of the
> apparent issues could be caused by the block device underneath the
> filesystem having changed size, so the filesystem's in some sense the wrong
> size now?
>
> Cheers,
>
> John.
>
> --
> 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
>



-- 
       Majed B.
--
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

  parent reply	other threads:[~2009-12-19 23:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16  5:40 RAID5 / 6 Growth Leslie Rhorer
2009-12-16  6:37 ` Majed B.
2009-12-16  8:06   ` Leslie Rhorer
2009-12-16  8:12     ` Michael Evans
2009-12-16  8:38       ` Leslie Rhorer
2009-12-16 11:21     ` Majed B.
2009-12-17  1:36       ` Leslie Rhorer
2009-12-19  1:13       ` Leslie Rhorer
2009-12-19 18:21         ` Leslie Rhorer
2009-12-19 18:36           ` Majed B.
2009-12-19 19:02             ` Leslie Rhorer
2009-12-19 19:55               ` Majed B.
2009-12-19 20:19                 ` Leslie Rhorer
2009-12-19 23:39                   ` John Robinson
2009-12-19 23:49                     ` Leslie Rhorer
2009-12-19 23:59                     ` Majed B. [this message]
2009-12-16 13:25     ` Goswin von Brederlow
2009-12-17  1:51       ` Leslie Rhorer
2009-12-17  9:27         ` John Robinson
2009-12-18  1:33           ` Leslie Rhorer
2009-12-19  1:11           ` Leslie Rhorer
2009-12-18 12:27         ` Goswin von Brederlow
2009-12-17 17:53     ` Bill Davidsen
2009-12-18  1:46       ` Leslie Rhorer
2009-12-19  1:12       ` Leslie Rhorer
     [not found] <70ed7c3e0912191232k7deb3a3p40ddd6bc1bdfd3ae@mail.gmail.com>
2009-12-19 21:05 ` Leslie Rhorer
2009-12-21 12:33   ` Goswin von Brederlow

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=70ed7c3e0912191559i75bdc191p55a93568b18f1652@mail.gmail.com \
    --to=majedb@gmail.com \
    --cc=linux-raid@vger.kernel.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).