Christian Laursen wrote:
Ivan Voras <[EMAIL PROTECTED]> writes:
Christian Laursen wrote:
However, with journaling you can have filesystem corruption and not know
about it. With fsck, bg or not, at least you will know.
Also, I'm interested about this - what kind of silent corruption? The
same kind that can generally come from on-drive caches?
Yes, as well as corruption resulting from bugs in the kernel code. The point
is that you will never know because you never check your filesystems.
Well, thats why i actually don't find journaling filesystems very sexy.
So the question is, if it is still safe to use fsck on a gjournal
enabled FS ?
Having a bgfsck running on a 1 TB volume is not so terrible when it
afterwards confirms a valid and consistent filesystem.. Just trusting
the journal is a false sense of security in my opinion.
my 2cp
Stephan
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
