Re: ffs_alloc panic patch
From: Colin Percival (colin.percival_at_wadham.ox.ac.uk)
Date: 08/27/04
- Previous message: Ken Smith: "Re: ffs_alloc panic patch"
- In reply to: Ken Smith: "Re: ffs_alloc panic patch"
- Next in thread: Ken Smith: "Re: ffs_alloc panic patch"
- Reply: Ken Smith: "Re: ffs_alloc panic patch"
- Reply: Pavel Merdine: "Re[2]: ffs_alloc panic patch"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 27 Aug 2004 12:55:39 -0700 To: Ken Smith <kensmith@cse.Buffalo.EDU>
At 12:36 27/08/2004, Ken Smith wrote:
> ... Here you again wind up in a
> situation where the filesystem data structures on the disk can
> become corrupted. Typically at some point the ffs code will
> recognize that the metadata is incorrect and again a panic is
> better than trying to carry on pretending nothing is wrong.
Shouldn't a corrupt filesystem be handled by forcibly dismounting it,
rather than invoking panic()? We certainly don't want to keep on using
a corrupt filesystem, but we should attempt to isolate a single failing
piece of hardware rather than allowing it to bring down the entire
system.
Colin Percival
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
- Previous message: Ken Smith: "Re: ffs_alloc panic patch"
- In reply to: Ken Smith: "Re: ffs_alloc panic patch"
- Next in thread: Ken Smith: "Re: ffs_alloc panic patch"
- Reply: Ken Smith: "Re: ffs_alloc panic patch"
- Reply: Pavel Merdine: "Re[2]: ffs_alloc panic patch"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]