tags 784890 moreinfo thx On 10 mai 2015, at 09:57, Tim Weippert <[email protected]> wrote:
> Package: flashybrid > Version: 0.18 > Severity: important > > Dear Maintainer, > > i hav an fresh jessie installation on an Alix Board (alix 2d13) with an CF > Card. I tried flashybrid > for the first time and was unable to sync ramstore directiories to real CF > Location. > > fh-sync run reports the following errors: > > root@indoor01:~# fh-sync > Syncing flashybrid system... > Synchronizing /var/lib/exim4mount: /ram/var/lib/exim4.flash is busy > . > Synchronizing /var/logmount: /ram/var/log.flash is busy > . > Synchronizing /var/runmount: /ram/var/run.flash is busy > . > Synchronizing /rootmount: /ram/root.flash is busy > . > Synchronizing /var/spoolmount: /ram/var/spool.flash is busy > . > Synchronizing /var/mailmount: /ram/var/mail.flash is busy > . > done. NB: there's not much I can do since I can't upload to debian anymore. This typically happens after a mounting parts of the filesystem read-write, followed by the installation/startup of some daemon. The daemon then opens a write file descriptor to the non-mirrored location (the actual media support), and when flashybrid tries to remount that media read-only, it fails. It does strike me as odd to find /root in the list though. Can you confirm that this happens (or not) immediately after booting a clean system (unmodified flashybrid) and /without/ installing or starting anything after a read-write mount. If it does, it would suggest that flashybrid is started too late in the boot process. T. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
