From: "Jeffrey E. Hundstad" <jeffrey.hundstad@mnsu.edu>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jakob Oestergaard <jakob@unthought.net>,
Christoph Hellwig <hch@infradead.org>,
David Greaves <david@dgreaves.com>, Jan Kasprzak <kas@fi.muni.cz>,
linux-kernel <linux-kernel@vger.kernel.org>,
kruty@fi.muni.cz
Subject: Re: journaled filesystems -- known instability; Was: XFS: inode with st_mode == 0
Date: Fri, 28 Jan 2005 15:06:13 -0600 [thread overview]
Message-ID: <41FAA945.3070106@mnsu.edu> (raw)
In-Reply-To: <1106946002.1988.88.camel@sisko.sctweedie.blueyonder.co.uk>
Stephen C. Tweedie wrote:
>Hi,
>
>On Fri, 2005-01-28 at 20:15, Jeffrey E. Hundstad wrote:
>
>
>
>>>>Does linux-2.6.11-rc2 have both the linux-2.6.10-ac10 fix and the xattr
>>>>problem fixed?
>>>>
>>>>
>
>
>
>>>Not sure about how much of -ac went in, but it has the xattr fix.
>>>
>>>
>
>
>
>>I've had my machine that would crash daily if not hourly stay up for 10
>>days now. This is with the linux-2.6.10-ac10 kernel.
>>
>>
>
>Good to know. Are you using xattrs extensively (eg. for ACLs, SELinux
>or Samba 4)?
>
>--Stephen
>
>
>
On the machines that were having problems we really weren't using them
for anything. I think I may have been running into the BIO problem that
was fixed in 2.6.10-ac10.
next prev parent reply other threads:[~2005-01-28 21:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 12:59 XFS: inode with st_mode == 0 Jan Kasprzak
2004-12-09 13:53 ` Jakob Oestergaard
2004-12-09 14:07 ` Jan Kasprzak
2004-12-09 21:54 ` Christoph Hellwig
2004-12-14 23:40 ` Jakob Oestergaard
2004-12-21 18:43 ` Jan Kasprzak
2004-12-22 8:41 ` Jakob Oestergaard
2004-12-22 18:23 ` Christoph Hellwig
2004-12-23 15:01 ` Jakob Oestergaard
2005-01-04 8:48 ` Jakob Oestergaard
2005-01-05 11:34 ` Christoph Hellwig
2005-01-14 18:14 ` David Greaves
2005-01-14 18:23 ` Jakob Oestergaard
2005-01-15 2:09 ` Nathan Scott
2005-01-17 0:53 ` Jakob Oestergaard
2005-01-16 13:51 ` Christoph Hellwig
2005-01-17 10:07 ` Jakob Oestergaard
2005-01-17 11:55 ` Jan-Frode Myklebust
2005-01-17 13:48 ` Anders Saaby
2005-01-17 21:31 ` journaled filesystems -- known instability; Was: " Jeffrey Hundstad
2005-01-17 20:54 ` Alan Cox
2005-01-20 22:30 ` Jeffrey E. Hundstad
2005-01-25 12:47 ` Stephen C. Tweedie
2005-01-25 15:09 ` Jeffrey Hundstad
2005-01-25 15:37 ` Stephen C. Tweedie
2005-01-28 20:15 ` Jeffrey E. Hundstad
2005-01-28 21:00 ` Stephen C. Tweedie
2005-01-28 21:06 ` Jeffrey E. Hundstad [this message]
2005-01-18 11:45 ` Jan Kasprzak
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=41FAA945.3070106@mnsu.edu \
--to=jeffrey.hundstad@mnsu.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=david@dgreaves.com \
--cc=hch@infradead.org \
--cc=jakob@unthought.net \
--cc=kas@fi.muni.cz \
--cc=kruty@fi.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.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