puredyne-team team mailing list archive

[Aymeric Mansoux <am-launchpad@xxxxxxx>]

This is perfectly safe and nothing to worry about, just annoying.

Each volume needs to be checked for errors every x mountings, but with
live scripts (live-initramfs for Puredyne, and casper for Ubuntu 10.10),
when the system boots it looks if there are any persistent volumes or
files to load the customized user settings. This can be done up to four
times for each volume, meaning that always booting on a live system will
make have your disks checks up to four time more than usual.

The only workaround is to pass as boot argument where the persistent
file/volume is or remove the persistent boot argument for no checks at
all (in which case you won't have your settings saved in between
reboots).

** Changed in: puredyne-live
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of puredyne
team, which is the registrant for Puredyne Live.
https://bugs.launchpad.net/bugs/507493

Title:
  live boot causes maximal mount count to be reached sooner

Status in Puredyne liveCD/DVD/USB/HD:
  Won't Fix

Bug description:
  boot from liveCD/liveDVD/liveUSB a few times and the maximal mount
  count of the permanent hard drive file system(s) are reached really
  quickly, which causes fsck on next boot of the permanent installed OS.

  conjecture: the filesystems get mounted and unmounted several times on
  each boot, as the live scripts try to find persistent snapshots for
  home and root, possibly also mount/umount while trying to find
  persistent filesystems for home and root.  in which case this is not
  puredyne specific...