Re: Sidetracked: why gjournal over soft-updates (Was: Re: UFS2 Journaling implementation detail)

2008-04-26 Thread Dieter
SU requires that data it once sends to the drive gets written immediately, not cached by the drive. Modern desktop drives don't do that They do if you set them to write-through cache instead of write-back cache. Modern SATA drives also provide NCQ. When is FreeBSD going to support NCQ?

Re: Sidetracked: why gjournal over soft-updates (Was: Re: UFS2

2008-04-22 Thread Wojciech Puchar
than SU The caching can be stopped by putting hw.ata.wc=0 into /boot/loader.conf. Doesn't that settle this point about safety? but that's not needed. UPS is enough. even if your machine will halt/crash/panic, drive cache will be written then. Since we use softupdates and others use

Sidetracked: why gjournal over soft-updates (Was: Re: UFS2 Journaling implementation detail)

2008-04-19 Thread Mel
On Friday 18 April 2008 17:40:04 Ivan Voras wrote: 5. Some UFS implementations avoid journaling and instead implement soft updates: they order their writes in such a way that the on-disk file system is never inconsistent, or that the only inconsistency that can be created in the

Re: Sidetracked: why gjournal over soft-updates (Was: Re: UFS2 Journaling implementation detail)

2008-04-19 Thread Ivan Voras
2008/4/19 Mel [EMAIL PROTECTED]: On Friday 18 April 2008 17:40:04 Ivan Voras wrote: 5. Some UFS implementations avoid journaling and instead implement soft updates: they order their writes in such a way that the on-disk file system is never inconsistent, or that the only

Re: Sidetracked: why gjournal over soft-updates (Was: Re: UFS2

2008-04-19 Thread Tore Lund
Ivan Voras wrote: 1) Soft-updates were created in a different time, with different requirements than modern hard drives (especially desktop hard drives) can deliver. Especially, SU requires that data it once sends to the drive gets written immediately, not cached by the drive. Modern desktop