Gruß aus Gelnhausen Stefan Blochberger ____________________________________________________________
Diese eMail kann mit Hilfe Ihrer Signatur (PGP) auf Echtheit überprüft werden. -> http://bit.ly/KgzpDr [ Internet-Seite: http://Stefan.Blochberger.de ] ----------------------------------------------------------- Avast Antivirus Free: http://www.avast.com/get/goYL2hTo ----------------------------------------------------------- > Beim Einkaufen Geld zurück bekommen (CashBack): > Yingiz: http://bit.ly/eUyLS1 Quipu: http://bit.ly/LWAOQ7 > iGraal: http://de.igraal.com/#werber=Darkwing1001 > Mein Amazon-Link: http://amzn.to/wfElPr > Kostenloser Onlinespeicher (2 GB): http://db.tt/PUAqWXg >> Instant Support (VNC): https://db.tt/HsuC2MoC ____________________________________________________________ Bildung ist das, was übrig bleibt, wenn man alles, was man in der Schule gelernt hat, vergisst. [Albert Einstein] ____________________________________________________________ Nr.: 22 von 220 -------- Original-Nachricht -------- Betreff: Bug#784890: flashybrid: Unable to Sync ramstore directories ... Von: Tim Weippert <we...@weiti.org> An: Datum: 13.05.2015 19:56 > > On Mon, May 11, 2015 at 09:15:54PM +0200, Thibaut Varène wrote: >> On 11 mai 2015, at 19:32, Tim Weippert <we...@weiti.org> wrote: >> >> >>> If i found another CF card i will try to install an fresh >>> wheezy and update to jessie without migration to systemd (think >>> this should be possible) maybe then we know if it is an systemd >>> or kernel fault. >> >> Thanks. First ensure it's working fine in Wheezy. > > I just installed an plain wheezy and all is fine with flashybrid. > Attached is an output of some mount statements > (flashybrid-wheezy-orig.txt). Second i installed an 3.16 Kernel > from Backports just to see if it is an kernel issue > (flashybrid-wheezy-bpo.txt), and with this scenario all fine, too. > > And third i made an dist-upgrade to jessie with the bpo kernel > running ... > > after the dist-upgrade process finished and before reboot i got the > odd situation with the tmpfs twice mounts: > > 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=31202,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,noexec,relatime,size=25272k,mode=755) > /dev/sda1 on / type ext4 > (rw,relatime,errors=remount-ro,data=ordered) tmpfs on /run/lock > type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on > /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=92920k) > 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 (rw,relatime,errors=remount-ro,data=ordered) tmpfs on > /var/lib/exim4 type tmpfs (rw,relatime,size=122880k) /dev/sda1 on > /ram/var/lib/logrotate.flash type ext4 > (rw,relatime,errors=remount-ro,data=ordered) tmpfs on > /var/lib/logrotate type tmpfs (rw,relatime,size=122880k) /dev/sda1 > on /ram/var/log.flash type ext4 > (rw,relatime,errors=remount-ro,data=ordered) tmpfs on /var/log type > tmpfs (rw,relatime,size=122880k) tmpfs on /ram/var/run.flash type > tmpfs (rw,nosuid,noexec,relatime,size=25272k,mode=755) tmpfs on > /run type tmpfs (rw,nosuid,noexec,relatime,size=25272k,mode=755) > /dev/sda1 on /ram/root.flash type ext4 > (rw,relatime,errors=remount-ro,data=ordered) tmpfs on /root type > tmpfs (rw,relatime,size=122880k) /dev/sda1 on /ram/var/spool.flash > type ext4 (rw,relatime,errors=remount-ro,data=ordered) tmpfs on > /var/spool type tmpfs (rw,relatime,size=122880k) /dev/sda1 on > /ram/var/mail.flash type ext4 > (rw,relatime,errors=remount-ro,data=ordered) tmpfs on /var/mail > type tmpfs (rw,relatime,size=122880k) rpc_pipefs on > /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) rpc_pipefs on > /run/rpc_pipefs type rpc_pipefs (rw,relatime) > > For this i think it isn't an kernel issue, it is like you imagined, > maybe an systemd issue. After the reboot this situation stays the > same. > > BUT, if i startup with init=/lib/sysvinit/init to get an sysvinit > start system back, problem persistsi (flashybrid-jessie.txt). I > don't know if we had an full sysvinit system or some systemd > invocations, but i don't see any systemd processes running. Maybe > an other change in some utils? mount? or similar ... > > Then i tried the following: > > Booted with Backport Kernel for Wheezy + init=/lib/sysvinit/init > and voila: Flashybrid works as expected > (flashybrid-jessie-wheezy-bpo-kernel-sysvinit.txt). > > Now i'm a little confused ... Kernel AND systemd issue? > > Cheers, tim > I'm not expirienced. But i played with the initscript of flashybrid. Now i am ended with an extra maountoption and the first test looks good! No tmpfs mounts on *.flash and fh-sync is also sying is working... here the mounts: [~] # mount |grep flash /dev/sda1 on /ram/etc.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) /dev/sda1 on /ram/root.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) /dev/sda1 on /ram/var/cache/ddclient.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) /dev/sda1 on /ram/var/cache/samba.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) /dev/sda1 on /ram/var/lib/dbus.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) /dev/sda1 on /ram/var/lib/exim4.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) /dev/sda1 on /ram/var/lib/logrotate.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) /dev/sda1 on /ram/var/lib/nfs.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) /dev/sda1 on /ram/var/lib/php5.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) /dev/sda1 on /ram/var/lib/samba.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) /dev/sda1 on /ram/var/log.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) tmpfs on /ram/var/run.flash type tmpfs (rw,nosuid,relatime,size=405148k,mode=755) /dev/sda1 on /ram/var/spool.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) /dev/sda1 on /ram/var/mail.flash type ext4 (ro,relatime,errors=remount-ro,data=ordered) But /var/run still in use ;( [~] # fh-sync Syncing flashybrid system... Synchronizing /etc . Synchronizing /root . Synchronizing /var/cache/ddclient . Synchronizing /var/cache/samba . Synchronizing /var/lib/dbus . Synchronizing /var/lib/exim4 . Synchronizing /var/lib/logrotate . Synchronizing /var/lib/nfs . Synchronizing /var/lib/php5 . Synchronizing /var/lib/samba . Synchronizing /var/log . Synchronizing /var/run mount: /ram/var/run.flash wird gerade benutzt . Synchronizing /var/spool . Synchronizing /var/mail . done. You just have to add "--make-private" to all mounts in /etc/init.d/flashybrid The file to download: https://dl.dropboxusercontent.com/u/1490505/HP-T5730/etc/init.d/flashybrid You may test and confirm that it is working, please --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. http://www.avast.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
