At 14:12 22-8-2002 -0500, Steve Lord wrote:
> Could you quickly list them (just curious) ?
Off the top of my head:
hitting a bug in filemap.c unlocking an unlocked page, seems to
be lvm related.
Needs fixes for a release.
corruption with the combination of fsx and heavy memory load
for an fs with a blocksize less than a page - does not happen
with the default 4K block size.
The new blocksize is experimental and you could put a warning message in.
a hang in unmount, or remount readonly - I only see this on
my laptop after using some vpn software, but I do not think
the vpn is related. I cannot hit it elsewhere, but something
similar has been reported.
Sounds complicated and hard to investigate.
the defragmenter seems to be able to go haywire and suck up
Ongoing work, these things happen ;)
version 2 logs have some end cases to shake out - make a small
log and pound on metadata really hard. If I make a larger log
then I cannot hit this.
Default the utilities for a release to a v1 log. If forcing a v2 log print
An oops in xfs_iget - or a hang depending on who you are, seems
to take very heavy load and a few cpus to hit.
Thats enough for now!
Although some points need fixing, a 1.1.1 release without the newer
functionality (or print a warning) might be a good idea. Bring out a 1.2
release when we are certain it is tested enough.
I Currently have a shortage of hardware to test v2 logs and software raid5.
Pursuing my manager for spares :)
Using 2.4.19(ish) here on a couple machines have proved succesful so far.
2.4.19-rc3-xfs 9:14am up 24 days (Internet gateway,squid cache, webserver,
mailserver 2Mbit, lightly loaded)
2.4.19-xfs 9:16am up 17 days (Test server nfs, samba, gigabit Ethernet,
Without any fancy features the kernel is running fine.
It might just be your lucky day, if you only knew.