Hi Thibaut, yes i can confirm, this happens in an fresh and newly started Jessie System.
The Config Files are the Files from the Package, i only commented /etc in ramstore File. /root is there already. No change from my side. I haven't started any daemons/processes rather than connect via SSH to the System. For your information my mount table looks after clean start like this: weiti@indoor01:~$ mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=29791,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,relatime,size=50556k,mode=755) /dev/sda1 on / type ext4 (ro,relatime,errors=remount-ro,data=ordered) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=22,pgrp=1,timeout=300,minproto=5,maxproto=5,direct) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) mqueue on /dev/mqueue type mqueue (rw,relatime) tmpfs on /ram type tmpfs (rw,relatime,size=122880k) tmpfs on /tmp type tmpfs (rw,relatime,size=122880k) tmpfs on /run/lock type tmpfs (rw,relatime,size=122880k) tmpfs on /var/lib/dhcp type tmpfs (rw,relatime,size=122880k) tmpfs on /var/lib/misc type tmpfs (rw,relatime,size=122880k) tmpfs on /var/lib/urandom type tmpfs (rw,relatime,size=122880k) tmpfs on /var/tmp type tmpfs (rw,relatime,size=122880k) /dev/sda1 on /ram/var/lib/exim4.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) tmpfs on /var/lib/exim4 type tmpfs (rw,relatime,size=122880k) tmpfs on /ram/var/lib/exim4.flash type tmpfs (rw,relatime,size=122880k) /dev/sda1 on /ram/var/log.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) tmpfs on /var/log type tmpfs (rw,relatime,size=122880k) tmpfs on /ram/var/log.flash type tmpfs (rw,relatime,size=122880k) tmpfs on /ram/var/run.flash type tmpfs (rw,nosuid,relatime,size=50556k,mode=755) tmpfs on /run type tmpfs (rw,nosuid,relatime,size=50556k,mode=755) tmpfs on /ram/var/run.flash type tmpfs (rw,nosuid,relatime,size=50556k,mode=755) /dev/sda1 on /ram/root.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) tmpfs on /root type tmpfs (rw,relatime,size=122880k) tmpfs on /ram/root.flash type tmpfs (rw,relatime,size=122880k) /dev/sda1 on /ram/var/spool.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) tmpfs on /var/spool type tmpfs (rw,relatime,size=122880k) tmpfs on /ram/var/spool.flash type tmpfs (rw,relatime,size=122880k) /dev/sda1 on /ram/var/mail.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) tmpfs on /var/mail type tmpfs (rw,relatime,size=122880k) tmpfs on /ram/var/mail.flash type tmpfs (rw,relatime,size=122880k) rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime) rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime) rpc_pipefs on /ram/var/run.flash/rpc_pipefs type rpc_pipefs (rw,relatime) rpc_pipefs on /ram/var/run.flash/rpc_pipefs type rpc_pipefs (rw,relatime) My thoughs are that these situation are my problem: /dev/sda1 on /ram/root.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) tmpfs on /root type tmpfs (rw,relatime,size=122880k) tmpfs on /ram/root.flash type tmpfs (rw,relatime,size=122880k) It seems that root.flash gets mounted twice, on ro from the cf card which is ok, the other (later?) mount is an rw tmpfs ... and every sync while go to the tmpfs i think. And after an reboot these changes are lost, because the tmpfs get cleared. When i change fh-sync to do an remount,ro,bind, no errors occures, but changes weren't synced to CF also. HTH, tim On Sun, May 10, 2015 at 08:26:23PM +0200, Thibaut Varène wrote: > tags 784890 moreinfo > thx > > On 10 mai 2015, at 09:57, Tim Weippert <we...@weiti.org> 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. -- Tim Weippert http://weiti.org - we...@weiti.org GPG Fingerprint - E704 7303 6FF0 8393 ADB1 398E 67F2 94AE 5995 7DD8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
