From: David Chinner <dgc@sgi.com>
To: Dawid 'Kuba' Chrzan <qba@f-net.pl>
Cc: xfs@oss.sgi.com
Subject: Re: XFS + RAID1 strange message
Date: Mon, 16 Jul 2007 12:25:18 +1000 [thread overview]
Message-ID: <20070716022518.GH12413810@sgi.com> (raw)
In-Reply-To: <20070713151058.GA24153@gepard>
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
> 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.
> 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.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-07-16 2:25 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 [this message]
2007-07-17 7:29 ` Dawid 'Kuba' Chrzan
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=20070716022518.GH12413810@sgi.com \
--to=dgc@sgi.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.