From: Eric Sandeen <sandeen@sandeen.net>
To: Juergen Urban <JuergenUrban@gmx.de>
Cc: xfs@oss.sgi.com
Subject: Re: BUG() in end_page_writeback(), stack overflows and system speed decrease with XFS over USB
Date: Fri, 20 Nov 2009 10:36:31 -0600 [thread overview]
Message-ID: <4B06C58F.5070203@sandeen.net> (raw)
In-Reply-To: <200911201723.48033.JuergenUrban@gmx.de>
Juergen Urban wrote:
> On Thursday 19 November 2009 19:00:16 Eric Sandeen wrote:
>> Juergen Urban wrote:
>>> Hello,
>>>
>>> my machine is running very unstable since I use XFS on an external USB
>>> harddisc (855 GByte XFS partition on 1TByte). One problem was the stack
>>> overflows caused by the large stack use of XFS, USB, SCSI and VFS in
>>> Linux 2.6.23.13. NFS on XFS caused much more stack overflows. I think I
>>> got around the stack overflows by disabling preemption, SMP and NFS in
>>> Linux, but I am not sure about it. I think that I didn't got a message
>>> from the stack overflow detection after this.
>> Are you on 4k stacks? To be honest I'd still expect things to be mostly
>> ok stack-wise even if so.
>
> No, I am using 8k stacks.
Hmm.
...
> Now I tried linux-2.6.31.6. My system hangs in the start scripts. Maybe this
> is caused by network scripts. I got the message that ehci_hcd need to be
> loaded before uhci_hcd and ohci_hcd. I skipped uhci_hcd and ohci_hcd in
> /etc/discover.conf. Now I have a higher performance with linux-2.6.23.13 and I
> can record 3 normal streams in parallel on the with USB and XFS. But it is
> still unstable. The last error what I got was in block_prepare_write
> (fs/buffer.c). This caused follow up errors in do_invalidate_page() called by
> xfs_get_blocks().
> Sometimes there are file system deadlocks. I can do everything, but not access
> the file system. Every try to access the file system leads to a deadlock of the
> program. This normally happens after a kernel exception.
I guess including the kernel messages you see would help us know what
might be going on.
...
>>> Is there an easy way to backup the data or replace the file system
>>> without kernel crash in between?
>> You should certainly be able to copy data off xfs via usb; if it's
>> failing, I guess we'll need more info to find out why, but I'd suggest
>> at least booting a newer livecd to do that copy and see if things fare
>> better.
>
> My idea was to shrink it and create a new partition where I can copy the data.
> As far as I understand I need to mount it for the shrink process, so I may
> have the problem of kernel exceptions while shrinking.
You can't shrink xfs, if that's what you mean.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-11-20 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 8:57 BUG() in end_page_writeback(), stack overflows and system speed decrease with XFS over USB Juergen Urban
2009-11-19 18:00 ` Eric Sandeen
2009-11-20 16:23 ` Juergen Urban
2009-11-20 16:36 ` Eric Sandeen [this message]
2009-11-20 17:08 ` Eric Sandeen
2009-11-21 1:00 ` Juergen Urban
2009-11-21 10:51 ` Michael Monnerie
2009-11-21 17:33 ` Juergen Urban
2009-11-21 22:04 ` Dave Chinner
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=4B06C58F.5070203@sandeen.net \
--to=sandeen@sandeen.net \
--cc=JuergenUrban@gmx.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