Re: kernel panic mounting /tmp - 6.2-PRERELEASE
- From: Oliver Fromme <olli@xxxxxxxxxxxxxxxxx>
- Date: Wed, 18 Oct 2006 09:31:36 +0200 (CEST)
Brooks Davis wrote:
It's known that an appropriately corrupt file system can do
this, but the causes (there are probably several) are not yet
known. There is some speculation that the only solution is
to add checksums to all key data sections.
Which means that ZFS will solve the problem, as soon as
PJD has finished the port to FreeBSD. ;-)
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.
$ dd if=/dev/urandom of=test.pl count=1
$ file test.pl
test.pl: perl script text executable
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"
- References:
- Re: kernel panic mounting /tmp - 6.2-PRERELEASE
- From: Brooks Davis
- Re: kernel panic mounting /tmp - 6.2-PRERELEASE
- Prev by Date: Re: ENABLE_SUID_SSH in make.conf
- Next by Date: hald and strange error messages
- Previous by thread: Re: kernel panic mounting /tmp - 6.2-PRERELEASE
- Next by thread: /etc/rc's purgedir (or /etc/rc.d/cleanvar in 6.0)
- Index(es):
Relevant Pages
|
|
