Re: UFS corruption panic

2012-01-15 Thread Joe Holden
Actually, that would be a safe assumption especially now that the installer rightly or wrongly defaults to a single / filesystem, but perhaps if it could be tunable via mount flags that would be sensible also... Thanks, J On Sun, Jan 15, 2012 at 12:48 PM, Bruce Cran wrote: > > On 15/01/2012 08:1

Re: UFS corruption panic

2012-01-15 Thread Bruce Cran
On 15/01/2012 08:12, Stefan Bethke wrote: Yes, a panic is the correct action here. While I agree that it's super annoying, the filesystem notices that something is *really* wrong. Instead of letting the problem fester and continue to corrupt data, it stops the system. One could argue instea

Re: UFS corruption panic

2012-01-15 Thread Daniel O'Connor
On 15/01/2012, at 18:42, Stefan Bethke wrote: > Most filesystems work under the assumption that they're the sole owner of the > disk. This means that any changes to the on-disk data must come from > filesystem code itself; if that data is inconstistent, it must be a bug in > the filesystem cod

Re: UFS corruption panic

2012-01-15 Thread Stefan Bethke
Am 15.01.2012 um 05:20 schrieb Joe Holden: > Guys > > Is a panic **really** appropriate for a filesystem that isn't even in > fstab? > > ie; > panic: ufs_dirbad: /mnt: bad dir ino 3229 at offset 0: mangled entry > > Which happened to be an file-backed md volume that got changed as I forgot

Re: UFS corruption panic

2012-01-14 Thread Garrett Cooper
On Sat, Jan 14, 2012 at 8:20 PM, Joe Holden wrote: >  Guys > > Is a panic **really** appropriate for a filesystem that isn't even in > fstab? > > ie; > panic: ufs_dirbad: /mnt: bad dir ino 3229 at offset 0: mangled entry > > Which happened to be an file-backed md volume that got changed as I f

UFS corruption panic

2012-01-14 Thread Joe Holden
Guys Is a panic **really** appropriate for a filesystem that isn't even in fstab? ie; panic: ufs_dirbad: /mnt: bad dir ino 3229 at offset 0: mangled entry Which happened to be an file-backed md volume that got changed as I forgot to unmount it beforehand, however as a result there is now inc

UFS corruption panic

2012-01-14 Thread Joe Holden
Guys Is a panic **really** appropriate for a filesystem that isn't even in fstab? ie; panic: ufs_dirbad: /mnt: bad dir ino 3229 at offset 0: mangled entry Which happened to be an file-backed md volume that got changed as I forgot to unmount it beforehand, however as a result there is now in