linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Majed B." <majedb@gmail.com>
To: Leslie Rhorer <lrhorer@satx.rr.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 / 6 Growth
Date: Sat, 19 Dec 2009 21:36:42 +0300	[thread overview]
Message-ID: <70ed7c3e0912191036o2a1d413es6492bdafc3a75267@mail.gmail.com> (raw)
In-Reply-To: <2F.73.01567.6991D2B4@cdptpa-omtalb.mail.rr.com>

Do any of the disks report sector errors or ATA or read errors?
smartctl -a /dev/sdx should give the report, assuming you run smartd
and have it probe disks periodically.

I've seen newer versions of the xfsprogs and libs packages. Try using
those. I know you're against new packages that haven't been included
in "stable" -- but if this is a dev/backup system, it's worth the shot
in my opinion.

Good luck.

On Sat, Dec 19, 2009 at 9:21 PM, Leslie Rhorer <lrhorer@satx.rr.com> wrote:
> Well, the RAID growth completed on the backup system, but now when I attempt
> to mount the XFS file system, mount returns the error "mount: Structure
> needs cleaning".  When I issue the xfs_repair command, I get this:
>
> Backup:/boot/grub# xfs_repair -v /dev/md0
> Phase 1 - find and verify superblock...
>        - block cache size set to 28616 entries
> Phase 2 - using internal log
>        - zero log...
> zero_log: head block 38584 tail block 38504
> ERROR: The filesystem has valuable metadata changes in a log which needs to
> be replayed.  Mount the filesystem to replay the log, and unmount it before
> re-running xfs_repair.  If you are unable to mount the filesystem, then use
> the -L option to destroy the log and attempt a repair.
> Note that destroying the log may cause corruption -- please attempt a mount
> of the filesystem before doing this.
>
>        The file system was shut down cleanly with umount prior to starting
> the growth, but xfs still seems to think the file system is dirty and the
> journal needs to be replayed.  Running xfs_repair with the -n command shows
> the file system has a few errors.  Before I purge the log and potentially
> lose a few files, is there something else I should try under mdadm to
> possibly fix teh array structure?  (I doubt it, but I wanted to check with
> others more knowledgeable than I before I proceed.)
>
> --
> 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

  reply	other threads:[~2009-12-19 18:36 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. [this message]
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.
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=70ed7c3e0912191036o2a1d413es6492bdafc3a75267@mail.gmail.com \
    --to=majedb@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lrhorer@satx.rr.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).