On Tue, Feb 12, 2008 at 01:02:05PM -0800, Linda Walsh wrote:
> David Chinner wrote:
> >Perhaps by running xfs_fsr manually you could reproduce the
> >problem while you are sitting in front of the machine...
>
> Um...yeah, AND with multiple "cp's of multi-gig files
> going on at same
Linda Walsh wrote:
>
> Eric Sandeen wrote:
>> Linda Walsh wrote:
>>> David Chinner wrote:
Filesystem bugs rarely hang systems hard like that - more likely is
a hardware or driver problem. And neither of the lockdep reports
below are likely to be responsible for a system wide,
Eric Sandeen wrote:
Linda Walsh wrote:
David Chinner wrote:
Filesystem bugs rarely hang systems hard like that - more likely is
a hardware or driver problem. And neither of the lockdep reports
below are likely to be responsible for a system wide, no-response
hang.
---
"Ish", the
Linda Walsh wrote:
>
> David Chinner wrote:
>> Filesystem bugs rarely hang systems hard like that - more likely is
>> a hardware or driver problem. And neither of the lockdep reports
>> below are likely to be responsible for a system wide, no-response
>> hang.
> ---
> "Ish", the 32-bitter,
David Chinner wrote:
Filesystem bugs rarely hang systems hard like that - more likely is
a hardware or driver problem. And neither of the lockdep reports
below are likely to be responsible for a system wide, no-response
hang.
---
"Ish", the 32-bitter, has been the only hard-hanger.
On Mon, Feb 11, 2008 at 05:02:05PM -0800, Linda Walsh wrote:
>
> I'm getting similar errors on an x86-32 & x86-64 kernel. The x86-64 system
> (2nd log below w/date+times) was unusable this morning: one or more of the
> xfs file systems had "gone off line" due to some unknown error (upon reboot,
On Mon, Feb 11, 2008 at 05:02:05PM -0800, Linda Walsh wrote:
I'm getting similar errors on an x86-32 x86-64 kernel. The x86-64 system
(2nd log below w/date+times) was unusable this morning: one or more of the
xfs file systems had gone off line due to some unknown error (upon reboot,
no
Eric Sandeen wrote:
Linda Walsh wrote:
David Chinner wrote:
Filesystem bugs rarely hang systems hard like that - more likely is
a hardware or driver problem. And neither of the lockdep reports
below are likely to be responsible for a system wide, no-response
hang.
---
Ish, the
Linda Walsh wrote:
David Chinner wrote:
Filesystem bugs rarely hang systems hard like that - more likely is
a hardware or driver problem. And neither of the lockdep reports
below are likely to be responsible for a system wide, no-response
hang.
---
Ish, the 32-bitter, has been the
On Tue, Feb 12, 2008 at 01:02:05PM -0800, Linda Walsh wrote:
David Chinner wrote:
Perhaps by running xfs_fsr manually you could reproduce the
problem while you are sitting in front of the machine...
Um...yeah, AND with multiple cp's of multi-gig files
going on at same time, both
Linda Walsh wrote:
Eric Sandeen wrote:
Linda Walsh wrote:
David Chinner wrote:
Filesystem bugs rarely hang systems hard like that - more likely is
a hardware or driver problem. And neither of the lockdep reports
below are likely to be responsible for a system wide, no-response
hang.
---
I'm getting similar errors on an x86-32 & x86-64 kernel. The x86-64 system
(2nd log below w/date+times) was unusable this morning: one or more of the
xfs file systems had "gone off line" due to some unknown error (upon reboot,
no errors were indicated; all partitions on the same physical disk).
I'm getting similar errors on an x86-32 x86-64 kernel. The x86-64 system
(2nd log below w/date+times) was unusable this morning: one or more of the
xfs file systems had gone off line due to some unknown error (upon reboot,
no errors were indicated; all partitions on the same physical disk).
I
13 matches
Mail list logo
