Hi there,

When a zone is booted with dirty filesystems, only an "fsck -m" is issued and 
checks the stauts of the filesystem. If the filesystem is not clean the zone 
boot aborts.

Question is why don't we use "fsck -p" instead of "fsck -m" the same way we 
treat system boot? This way only serious file system inconsistence needs manual 
intervention, just like whole system boot up.


This message posted from opensolaris.org
zones-discuss mailing list

Reply via email to