public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kent Fredric" <kentfredric@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] XFS problems
Date: Sun, 3 Jun 2007 02:33:55 +1200	[thread overview]
Message-ID: <8cd1ed20706020733o6204e162jba3006c23cf5ddd6@mail.gmail.com> (raw)
In-Reply-To: <1180528604.6308.24.camel@omc-2.omesc.com>

[-- Attachment #1: Type: text/plain, Size: 2139 bytes --]

On 5/31/07, Jules Colding <colding@omesc.com> wrote:
>
> On Wed, 2007-05-30 at 08:24 -0400, Randy Barlow wrote:
> > Jules Colding wrote:
> > > May 30 10:29:40 omc-2 [10822.156355] sd 0:4:1:0: SCSI error: return
> code = 0x00040001
> > > May 30 10:29:40 omc-2 [10822.156423] end_request: I/O error, dev sdb,
> sector 97564151
> > > May 30 10:29:46 omc-2 [10827.996196] I/O error in filesystem ("sdb1")
> meta-data dev sdb1 block 0x88b5ac3       ("xlog_iodone") error 5 buf count
> 11776
> > > May 30 10:29:46 omc-2 [10827.996210] xfs_force_shutdown(sdb1,0x2)
> called from line 960 of file fs/xfs/xfs_log.c.  Return address =
> 0xffffffff80398b06
> > > May 30 10:29:46 omc-2 [10827.996299] Filesystem "sdb1": Log I/O Error
> Detected.  Shutting down filesystem: sdb1
> > > May 30 10:29:46 omc-2 [10827.996305] Please umount the filesystem, and
> rectify the problem(s)
> > > May 30 10:29:46 omc-2 [10827.996983] sd 0:4:1:0: SCSI error: return
> code = 0x00040001
> > > May 30 10:29:46 omc-2 [10827.996986] end_request: I/O error, dev sdb,
> sector 63
> >
> > Those to me look like you are having hardware issues...
>
> My guess too, but I'm confused by the fact that these problems continue
> even though I've put the only disk reported to have errors offline. Can
> an offline disk provoke errors in the remaining array?
>
> Thanks,
>   jules
>
>
> --
> gentoo-user@gentoo.org mailing list
>
>
I've had those problems, and they're a real PITA. In my case i had to
re-arrange my cables 15 umpteen hundred times before they would position so
I didn't get any loss of contact, and turn of athcool . ( yes, athcool, if
you have it, could be your problem, i didn't believe it at first myself )

A drive doesn't have to be even mounted for those errors to show up, but it
sure helps. My recommendation is if you have a disk which is frequently
dropping out on you like that, you switch to JFS, XFS really doesn't play
nice if it thinks the drive is plugged in twice ....., and JFS has
impressive recovery ability.


-- 
Kent
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x|
print "enNOSPicAMreil kdrtf@gma.com"[(2*x)..(2*x+1)]}'

[-- Attachment #2: Type: text/html, Size: 2732 bytes --]

      reply	other threads:[~2007-06-02 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30  8:37 [gentoo-user] XFS problems Jules Colding
2007-05-30 12:24 ` Randy Barlow
2007-05-30 12:36   ` Jules Colding
2007-06-02 14:33     ` Kent Fredric [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=8cd1ed20706020733o6204e162jba3006c23cf5ddd6@mail.gmail.com \
    --to=kentfredric@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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