public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Ling Ho <ling@slac.stanford.edu>
Cc: xfs@oss.sgi.com
Subject: Re: RHEL 6.x xfs mount causing panic after forced shutdown
Date: Fri, 21 Sep 2012 16:59:53 -0500	[thread overview]
Message-ID: <505CE359.7020707@sandeen.net> (raw)
In-Reply-To: <505CE0CA.6090005@slac.stanford.edu>

On 9/21/12 4:48 PM, Ling Ho wrote:
> Hi,
> 
> I am facing a problem when my servers get power cycled by force. When they come up, almost everytime when xfs filesystems are being mounted, I get a system panic.

Hm, you didn't include the panic itself, though.

But bugs for distros like RHEL (or RHS, perhaps) should probably be reported to your Red Hat Support contacts, rather than taken to the upstream mailing list...

-Eric

> It looks like what's described here:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=657166
> 
> But I am running RHEL 6.2 and 6.3 (2.6.32-279.el6.x86_64)
> 
> This is what my fstab entrys look like:
> 
> LABEL=/brick1                /brick1                 xfs sunit=256,swidth=3328,noatime,nodiratime,logbufs=8,largeio,quota 0 0
> 
> 
> # xfs_info /brick1
> meta-data=/dev/sdb               isize=256    agcount=24, agsize=268435200 blks
>          =                       sectsz=512   attr=2
> data     =                       bsize=4096   blocks=6347161600, imaxpct=5
>          =                       sunit=32     swidth=416 blks
> naming   =version 2              bsize=4096   ascii-ci=0
> log      =internal               bsize=4096   blocks=521728, version=2
>          =                       sectsz=512   sunit=8 blks, lazy-count=1
> realtime =none                   extsz=4096   blocks=0, rtextents=0
> 
> 
> Even if I go to single user mode and try to mount (via the fstab entry), I get the panic. But I can mount it without any option by doing "mount /dev/sdb /brick1".
> 
> Is there any workaround to this?
> 
> Thanks,
> ...
> ling
> 
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2012-09-21 21:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 21:48 RHEL 6.x xfs mount causing panic after forced shutdown Ling Ho
2012-09-21 21:59 ` Eric Sandeen [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=505CE359.7020707@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=ling@slac.stanford.edu \
    --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