From: Eric Sandeen <sandeen@sandeen.net>
To: Ian Williamson <notian@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Software raid 5 with XFS causing strange lockup problems
Date: Wed, 11 Oct 2006 08:53:52 -0500 [thread overview]
Message-ID: <452CF770.5050902@sandeen.net> (raw)
In-Reply-To: <acd894d40610102307n7fd07108u67d1b1015eeeb594@mail.gmail.com>
Ian Williamson wrote:
> I am running XFS on a software raid 5. I am doing this with a PCI
> controller with 4 SATA drives attached to it.
>
> When I play my music over the network through Samba from the raid
> volume my audio client will often loose the connection. This isn't
> remediated until I restart the machine with the raid controller or
> wait for an unknown amount of time. Either way, the problem still
> persists.
>
> Initially I though that this was Samba's fault, but I think it may be
> xfs related due to what was in /var/log/messages:
>
> Oct 9 22:37:33 ionlinux kernel: [105657.982701] Modules linked in:
> serio_raw i2c_nforce2 pcspkr forcedeth r8169 nvidia_agp agpgart
> i2c_core psmouse sg evdev xfs dm_mod sd_mod generic sata_nv ide_disk
> ehci_hcd ide_cd cdrom sata_sil ohci_hcd usbcore libata scsi_mod
> ide_generic processor
> Oct 9 22:37:33 ionlinux kernel: [105657.982985] EIP:
> 0060:[<f8a1353e>] Not tainted VLI
> Oct 9 22:37:33 ionlinux kernel: [105657.982986] EFLAGS: 00010246
> (2.6.18 #1)
It looks like you've edited this a bit too much, what came before this in the logs?
Are you running on 4k stacks, out of curiosity?
-Eric
next prev parent reply other threads:[~2006-10-11 14:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 6:07 Software raid 5 with XFS causing strange lockup problems Ian Williamson
2006-10-11 13:53 ` Eric Sandeen [this message]
2006-10-11 16:21 ` Ian Williamson
2006-10-11 16:36 ` Eric Sandeen
2006-10-11 17:19 ` [UNSURE] " Justin Piszcz
2006-10-11 18:41 ` Ian Williamson
2006-10-11 18:42 ` Justin Piszcz
2006-10-11 19:10 ` Ian Williamson
2006-10-12 1:12 ` Timothy Shimmin
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=452CF770.5050902@sandeen.net \
--to=sandeen@sandeen.net \
--cc=notian@gmail.com \
--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