Subject: Re: Strange/weird '*fs' effects in -current (1.5Q till now)
To: None <firstname.lastname@example.org>
From: Jaromír <email@example.com>
Date: 02/20/2001 10:58:26
there have been couple of fs fixes recently, including some nfs fixes.
You might try to update your kernel, maybe it would help.
Markus W Kilbinger wrote:
> Maybe in relation to
> I noticed the following misbehavior of -current systems (1.5Q till
> now, at least i386 and sparc), quite easy to reproduce: Create/take an
> intact mailbox file (e. g. several 'echo skajdkjadajld | mail -s ""
> kilbi' and taking the resulting '/var/mail/kilbi' file), put it on an
> nfs mounted folder (the nfs servers OS doesn't seem to matter) and try
> to modify (especially deleting some mails in the middle) it with
> 'mutt' or 'pine' with a -current nfs client: Afterwards the mailbox
> file is disrupted! :-(
> Modifying local mailbox files works correctly on -current.
> -> nfs/ubc/uvm problem? Known? send-pr?
> Second strange *fs thing (only i386 proven): With release 1.5 I was
> quite happy to be able to play some movie files with xanim, especially
> wasabi.mov (buds commercial). With -current systems I get (same xanim
> binary and wasabi.mov!):
> - '... QT: no video/audio to play. possibly truncated. ...', if
> 'wasabi.mov' is located on a local ffs or nfs mounted.
> - a correct 'wasabi.mov' play, if 'wasabi.mov' is accessed on a
> mounted cdrom! (It's really the same 'wasabi.mov' file!)
> -> Same problem category?
> Can anybody confirm these 'stable' problems?
> (I also see some -current crashes as nfs server under heavy nfs load,
> but get no kernel core dumps after reboot...)
> And, of course, any help appreciated,
Jaromir Dolecek <jdolecek@NetBSD.org> http://www.ics.muni.cz/~dolecek/
@@@@ Wanna a real operating system ? Go and get NetBSD, dammit! @@@@