On Tuesday 17 July 2007 08:09:48 Nico -telmich- Schottelius wrote: > Anyone an idea why it aborts and how to fix?
An idea why it aborts _could_ be the fact that the Linux (kernel) NFS-server (there's also a userland NFS server, but that's not widely used, so I presume this isn't the case for you) doesn't unlink files that are unlinked from remote immediately, but moves them to a temporary (.nfs<someid>) name before finally truly unlinking them in case the file is still referenced by some NFS handle (i.e., opened at the remote end), thus causing the directory to not be empty, even though all files in it have actually been unlinked from the remote end. I don't know whether some performance/caching issues cause this, but as the temporary (seemingly) disappeared when bonnie++ was closed (and thus all file descriptors of bonnie among with any cache the OS kept freed), I'd guess in this direction. Again, this is just a wild guess, and I've never had problems running bonnie++ on a Linux Kernel-NFS-server exported filesystem, but from Linux NFS-clients, that is, which might (or rather, will probably) behave differently. -- Heiko Wundram Product & Application Development ------------------------------------- Office Germany - EXPO PARK HANNOVER Beenic Networks GmbH Mailänder Straße 2 30539 Hannover Fon +49 511 / 590 935 - 15 Fax +49 511 / 590 935 - 29 Mail [EMAIL PROTECTED] Beenic Networks GmbH ------------------------------------- Sitz der Gesellschaft: Hannover Geschäftsführer: Jorge Delgado Registernummer: HRB 61869 Registergericht: Amtsgericht Hannover _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"