Hello,

I have a mid-loaded server which runs each daemon in jail()-ed
environments.  The data space is union-mounted, because nullfs paniced the
kernel when someting did a chroot on it (this was the case with
4.2-STABLE).

On friday I upgraded from 4.3-RC to the latest 4.3-STABLE and noticed that
nullfs actually works, but I get a lot of errors, similar to these:

Jun 15 18:21:59 insomnia /kernel: object inconsistant state: RPC: 1, RC: 0
Jun 15 18:22:39 insomnia /kernel: object inconsistant state: RPC: 3282, RC: 0
Jun 15 18:22:39 insomnia /kernel: object inconsistant state: RPC: 1, RC: 0
Jun 15 18:23:10 insomnia /kernel: object inconsistant state: RPC: 3282, RC: 0
Jun 15 18:23:10 insomnia /kernel: object inconsistant state: RPC: 1, RC: 0
Jun 15 18:24:03 insomnia /kernel: object inconsistant state: RPC: 3282, RC: 0
Jun 15 18:24:03 insomnia /kernel: object inconsistant state: RPC: 1, RC: 0

when something accesses the filesystem. I have clean filesystems and have
nothing to do with NFS.

Because of the above errors, my system still uses unionfs, but it has a
very annoying problem. When a program sends data from a unionfs mounted
filesystem with sendfile() the data gets corrupted (tried with several
daemons).

I did nearly 800 GB (smashed up) traffic, when somebody finally noted
this, so I had to patch all of the used daemons, like the standard ftpd to
not to use sendfile().

BTW, unionfs seems to be working better than in the 4.2 days, so I think
more and more people will use it. Please if you can, fix this error and if
you can't, note this problem in the manpage.

For the nullfs problem, I would be glad to know, what does this mean :)


Thanks,
--------------------------------------------------------------------------
Attila Nagy                                    e-mail:  [EMAIL PROTECTED]
Budapest Polytechnic (BMF.HU)                   @work: +361 210 1415 (194)
H-1084 Budapest, Tavaszmezo u. 15-17.           cell.: +3630 306 6758


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to