From: Carlos Maiolino <cmaiolino@redhat.com>
To: Malte Gell <mailinglisten@posteo.de>
Cc: XFS <xfs@oss.sgi.com>
Subject: Re: hard reboot, no XFS messages
Date: Fri, 10 Apr 2015 13:31:51 -0300 [thread overview]
Message-ID: <20150410163151.GA1017@hades.maiolino.org> (raw)
In-Reply-To: <296cad845fb1a5c610adf6d9975d3a95@posteo.de>
On Thu, Apr 09, 2015 at 02:52:55AM +0200, Malte Gell wrote:
> Hi there,
> I´m totally new to XFS.
>
> Recently my Linux box was stuck and I had to reboot it hard.
> After the reboot I was surprised, there were no error messages or corrupt
> inodes.
>
> Usually on my ext4 root partition there are always some damaged inodes that
> get deleted. But my /home XFS partition seemed to have suffered zero effect
> from cold reboot.
>
> Is this normal for XFS that a cold reboot is handled that smooth?
>
> The XFS /home partition was created with Linux kernel 3.16.3.
>
> The only messages I saw in /var/log/messages was this:
>
> SGI XFS with ACLs, security attributes, realtime, large block/inode numbers,
> no debug enabled
> XFS (dm-0): Mounting V4 Filesystem
> XFS (dm-0): Starting recovery (logdev: internal)
> XFS (dm-0): Ending recovery (logdev: internal)
>
> On the net some people say XFS was very robust, but I did not expect it is
> that smooth after a cold reset... And other people said they were in hell
> with XFS...
>
> Thanks
>
Yes, it is normal, welcome to XFS :)
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
--
Carlos
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-04-10 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 0:52 hard reboot, no XFS messages Malte Gell
2015-04-09 2:14 ` Dave Chinner
2015-04-10 16:31 ` Carlos Maiolino [this message]
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=20150410163151.GA1017@hades.maiolino.org \
--to=cmaiolino@redhat.com \
--cc=mailinglisten@posteo.de \
--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