tags #292290 important
stop
newer xfs would have needed serious core changes in 2.6.8.
the debian kernel team had been penalized by the unforseen
long sarge core freeze.
it's very unfortunate as xfs in debian's kernel had
special attention. ext2, ext3 is recommended for 2.6.8 usage.
if you are
Op za 17 dec 2005 om 03:29:04 +0100 schreef maximilian attems:
backports.org has newer semi-official builds.
take care regarding the udev version while using such backports.
FWIW, thanks to Wessel Dankers, various builds of 2.6 images for sarge
(currently 2.6.13.4, with usable xfs support)
Hi,
On jeu, fév 03, 2005, Loïc Minier wrote:
So I'm about to get a fresh xfsprogs or a live CD and xfs_repair my FS
to get a log and send it upstream.
I've lost my log, I successfully uploaded it to another box, but the
box was running an evil OS which decided that it wouldn't
Hi,
This is a followup for Debian bug http://bugs.debian.org/292290.
Joost van Baal [EMAIL PROTECTED] - Wed, Jan 26, 2005:
`./lib/modules/2.6.10-1-k7/kernel/drivers/atm/zatm.ko': Unknown error 990
I've heard of one other victim of this problem with this kernel.
Wessel Dankers [EMAIL
Package: kernel-image-2.6.8-1-k7
Version: 2.6.8-10
Severity: critical
Justification: causes serious data loss
Hi,
[This is gonna be a sloppy bugreport; however, I still feel the problem
needs to be reported.]
In the last couple of days, 2 of my systems suffered major filesystem
corruption.
5 matches
Mail list logo
