My userland and kernel were rebuilt after running cvsup on Christmas day.
Right after that, files created on /tmp which is swap-backed get corrupted

I was trying to build mozilla and everytime I untarred the source into /tmp,
I would get about 10 random files corrupted. Each of these files has one
or two chunks of data replaced with null bytes (^@).

However, I didn't get the same error whenever I untarred into a physical disk
backed filesystem.

Has anyone experienced this problem? Can someone please try and confirm?


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

Reply via email to