Changes between Initial Version and Version 2 of Ticket #257


Ignore:
Timestamp:
Nov 8, 2011, 2:25:25 AM (13 years ago)
Author:
ezyang
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #257

    • Property Priority changed from normal to major

  • Ticket #257 – Description

    initial v2  
    11In checking up on assertions that running fsck on our ext2 AFS cache partition on boot (in the event of a crash) is going to be painful, I realized that (since it's listed with fs_passno 0) the AFS cache partition is never going to be fsck'd on boot. I suspect how this will play out is that it will fail to mount (because the kernel can't do journal recovery and call it done), the boot process will continue, and AFS will start up using the _mount point_ /usr/vice/cache on the root filesystem as its cache, which will boot promptly, but be subtly painful in other ways.
    22
    3 I'm not really seeing a good way to address this other than editing /etc/rc/rc.sysinit to have the logic we want (attempt to mount the partition, and if that fails mkfs and reattempt to mount it).
     3I'm not really seeing a good way to address this other than editing /etc/rc.d/rc.sysinit to have the logic we want (attempt to mount the partition, and if that fails mkfs and reattempt to mount it).