public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dawid 'Kuba' Chrzan" <qba@f-net.pl>
To: xfs@oss.sgi.com
Subject: Re: XFS + RAID1 strange message
Date: Tue, 17 Jul 2007 09:29:44 +0200	[thread overview]
Message-ID: <20070717072944.GA27270@gepard> (raw)
In-Reply-To: <20070716022518.GH12413810@sgi.com>

On Mon, Jul 16, 2007 at 12:25:18PM +1000, David Chinner wrote:
> On Fri, Jul 13, 2007 at 05:10:58PM +0200, Dawid 'Kuba' Chrzan wrote:
> > Hi
> > 
> > I got linux box
> > Linux gepard 2.6.17-pp3 #6 SMP Tue Feb 13 12:50:39 CET 2007 i686 unknown
> 
> You *really* don't want to be using that kernel for XFS. Please
> upgrade to at least 2.6.17.7 to avoid the dir2 corruption bug
> in that release.
> 
> http://oss.sgi.com/projects/xfs/faq.html#dir2

It seems that i have to upgrade on all servers.

> 
> > When i reboot , halt the server i always get 
> > Jul 12 18:25:14 gepard kernel: Starting XFS recovery on filesystem: md2
> > (logdev: internal)
> > Jul 12 18:25:14 gepard kernel: Ending XFS recovery on filesystem: md2
> > (logdev: internal)
> > 
> > such errors. Only on md2.
> > qba@gepard:~$ mount  | grep md2
> > /dev/md2 on /usr type xfs (rw)
> 
> I assume you mean when the system boots - those timestamps are from your
> boot log above. What is it that you think is incorrect about these
> messages? They are information indicating a successful log recovery
> which means your /usr filesystem is not being cleanly unmounted by your
> shutdown scripts. This is just saying that log recover occurred on
> that filesystem and everything is ok.
> 

Yes , these are system boot logs. 
I understand completely that this is log informing about recovery of
log.
But why ? It seems that i have to investigate why /usr was not clenly
unmounted.

> > Is it normal message , and i should not worry about it?
> 
> Yes, you'll see this message for any filesystem that wasn't cleanly
> unmounted and if it succeeds then you have nothing to worry about.
> 

I know i know.... I was thinking rather about this if it is usual on
raid1 - or some bug with xfs on raid.

Thanks for help and advice.


-- 
Pozdrawiam, Dawid 'Kuba' Chrzan
http://f-net.pl  qba_nospam_@f-net.pl
RLU#212729   net/sys administrator

"Computer games don't affect kids; I mean if Pac-Man affected us as
kids, we'd all be running around in darkened rooms, munching magic pills
and listening to repetitive electronic music." - Kristian Wilson,
Nintendo Inc., 1989.

  reply	other threads:[~2007-07-17  7:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-13 15:10 XFS + RAID1 strange message Dawid 'Kuba' Chrzan
2007-07-13 16:14 ` Justin Piszcz
2007-07-16  2:31   ` David Chinner
2007-07-16  2:25 ` David Chinner
2007-07-17  7:29   ` Dawid 'Kuba' Chrzan [this message]
2007-07-17 10:05     ` David Chinner
2007-07-17 13:10       ` Dawid 'Kuba' Chrzan

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=20070717072944.GA27270@gepard \
    --to=qba@f-net.pl \
    --cc=xfs@oss.sgi.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