On Sun, Jun 29, 2008 at 8:30 PM, Matthew Gardiner <[EMAIL PROTECTED]> wrote:
> I think Kyle might be onto something here. With ZFS it is so easy >> to create file systems, one could expect many people to do so. >> In the past, it was so difficult and required planning, so people >> tended to be more careful about mount points. >> >> In this new world, we don't really have a way to show which >> (ZFS) file systems are critical during boot (AFAICT). However, >> if we already know that a file system create failed in this manner, >> we could set the "canmount" property to false. This bothers me, >> just a little, because if there is such an error, it would be propagated >> as another potential latent fault. OTOH, as currently implemented, >> it is a different, and IMHO more impactful, latent fault. Thoughts? >> -- richard > > > Hi, > > I would have thought that the computer to keep loading, and once fully > loaded, a polite message stating which devices couldn't be mounted at boot > time - I mean, I assumed that would be a pretty obvious way of handling > something that couldn't be mounted. > > Matthew > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > > And what happens if it's your root volume? Politely keep booting until it kernel panics? Hope nothing is corrupted in the process?
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
