-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After some more testing it's entirely plausible (though unfortunately we
don't have anything conclusive) that we have a hardware problem.
Having added a new drive (hdc as reported below) and booted root=/dev/hdc2
with nothing mounted on hda, we have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After some more testing it's entirely plausible (though unfortunately we
don't have anything conclusive) that we have a hardware problem.
Having added a new drive (hdc as reported below) and booted root=/dev/hdc2
with nothing mounted on hda, we have
Hmm, we 'released' version 1 of XFS against a 2.4.2 base - and packaged
it into a RedHat 7.1 Kernel RPM, we also have a development CVS tree
currently running at 2.4.4. If you are running a production server
with what you describe below, you might want to switch to one of the
other two kernels I
hi,
i use kernel 2.4.3 with xfs (release 1) on a dell poweredge 2450.
it happens about every week that the system completely hangs (network
down,console does not accept
any input,sysreq useless...).
i think this has anything to do with xfs or other fs issues,because kupdated
always uses about
hi,
i use kernel 2.4.3 with xfs (release 1) on a dell poweredge 2450.
it happens about every week that the system completely hangs (network
down,console does not accept
any input,sysreq useless...).
i think this has anything to do with xfs or other fs issues,because kupdated
always uses about
Hmm, we 'released' version 1 of XFS against a 2.4.2 base - and packaged
it into a RedHat 7.1 Kernel RPM, we also have a development CVS tree
currently running at 2.4.4. If you are running a production server
with what you describe below, you might want to switch to one of the
other two kernels I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> However, in testing a directory with lots (~177000) of files, we get the
>> following oops (copied by hand, and run through ksymoops on a Red Hat box
>> since the Debian one segfaulted :( )
>Can you describe your testing beyond using a directory
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> [ I'm not subscribed to linux-xfs, please cc me ]
>
> We have managed to get a Debian potato system (with the 2.4 updates from
> http://people.debian.org/~bunk/debian plus xfs-tools which we imported
> from woody) to run 2.4.3-XFS.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
[ I'm not subscribed to linux-xfs, please cc me ]
We have managed to get a Debian potato system (with the 2.4 updates from
http://people.debian.org/~bunk/debian plus xfs-tools which we imported
from woody) to run 2.4.3-XFS.
However, in testing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
[ I'm not subscribed to linux-xfs, please cc me ]
We have managed to get a Debian potato system (with the 2.4 updates from
http://people.debian.org/~bunk/debian plus xfs-tools which we imported
from woody) to run 2.4.3-XFS.
However, in testing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
[ I'm not subscribed to linux-xfs, please cc me ]
We have managed to get a Debian potato system (with the 2.4 updates from
http://people.debian.org/~bunk/debian plus xfs-tools which we imported
from woody) to run 2.4.3-XFS.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
However, in testing a directory with lots (~177000) of files, we get the
following oops (copied by hand, and run through ksymoops on a Red Hat box
since the Debian one segfaulted :( )
Can you describe your testing beyond using a directory with
12 matches
Mail list logo
