Re: FFS data integrity

2006-06-21 Thread Bob Johnson
On 6/18/06, Pablo Marín Ramón [EMAIL PROTECTED] wrote: Bob Johnson wrote: The short answer is that fsck can detect the bad inodes and fix or delete them. Assuming no programming errors, you don't have to worry about a file containing bogus data after fsck has run. Unfortunately, if

Re: FFS data integrity

2006-06-18 Thread Pablo Marín Ramón
The short answer is that fsck can detect the bad inodes and fix or delete them. Assuming no programming errors, you don't have to worry about a file containing bogus data after fsck has run. Unfortunately, if write-caching is enabled on your hard drive (and it probably is, for speed), then

FFS data integrity

2006-06-16 Thread Pablo Marín Ramón
Here goes a newbie question about classical FFS (without softupdates). As metadata is updated synchronously, can an i-node, at some point, end pointing to not written yet data blocks? Is this a security risk, i.e., can those pointed to data blocks pertain to another user's deleted on memory but

Re: FFS data integrity

2006-06-16 Thread Bob Johnson
On 6/16/06, Pablo Marín Ramón [EMAIL PROTECTED] wrote: Here goes a newbie question about classical FFS (without softupdates). As metadata is updated synchronously, can an i-node, at some point, end pointing to not written yet data blocks? Is this a security risk, i.e., can those pointed to data