Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Thibaut VARENE]

> Le 9 juil. 2016 à 17:53, Andreas Beckmann  a écrit :
> 
> On Sun, 8 Nov 2015 11:24:34 +0100 Tim Weippert  wrote:
>> DM's not allowed to do an NMU Upload. Sorry, can't help. 
> 
>>> On Sun, May 17, 2015 at 03:00:24PM +0200, Thibaut Varène wrote:
 For the records, I'm attaching source for flashybrid-0.19 and a patch from 
 0.18 to this bug report. I can't upload it to the archive, but if some DD 
 wants to, let them be my guest.
> 
> What about uploading to mentors.debian.net and filing a RFS?

I don’t need a sponsor. The package needs a DD. I used to be one, now that’s 
over.

Best,
T.

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Andreas Beckmann]

On Sun, 8 Nov 2015 11:24:34 +0100 Tim Weippert  wrote:
> DM's not allowed to do an NMU Upload. Sorry, can't help. 

> > On Sun, May 17, 2015 at 03:00:24PM +0200, Thibaut Varène wrote:
> > > For the records, I'm attaching source for flashybrid-0.19 and a patch 
> > > from 0.18 to this bug report. I can't upload it to the archive, but if 
> > > some DD wants to, let them be my guest.

What about uploading to mentors.debian.net and filing a RFS?

Andreas

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Tim Weippert]

HI, 

DM's not allowed to do an NMU Upload. Sorry, can't help. 

cheers, 
tim

On Sun, Nov 08, 2015 at 10:55:03AM +0100, Tim Weippert wrote:
> HI, 
> 
> i prepared an NMU and try to upload it. Don't know if i'm allowed to do so 
> ... will see.
> 
> I also included the italian translation to the new package and your fix. 
> Hopefully it is ok.
> 
> Cheers, 
> tim
> 
> On Sun, May 17, 2015 at 03:00:24PM +0200, Thibaut Varène wrote:
> > OK, thanks everybody.
> > 
> > For the records, I'm attaching source for flashybrid-0.19 and a patch from 
> > 0.18 to this bug report. I can't upload it to the archive, but if some DD 
> > wants to, let them be my guest.
> > 
> > T.
> > 
> > 
> 
> 
> 
> 
> 
> -- 
> Tim Weippert
> http://weiti.org - we...@weiti.org
> GPG Fingerprint - E704 7303 6FF0 8393 ADB1  398E 67F2 94AE 5995 7DD8

-- 
Tim Weippert
http://weiti.org - we...@weiti.org
GPG Fingerprint - E704 7303 6FF0 8393 ADB1  398E 67F2 94AE 5995 7DD8

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Thibaut Varène]

Thanks for trying still.

I have put up a small webpage for flashybrid anyway, since it seems to be 
abandoned upstream:
http://hacks.slashdirt.org/sw/flashybrid/

T.

> On 08 Nov 2015, at 11:24, Tim Weippert  wrote:
> 
> HI, 
> 
> DM's not allowed to do an NMU Upload. Sorry, can't help. 
> 
> cheers, 
> tim
> 
> On Sun, Nov 08, 2015 at 10:55:03AM +0100, Tim Weippert wrote:
>> HI, 
>> 
>> i prepared an NMU and try to upload it. Don't know if i'm allowed to do so 
>> ... will see.
>> 
>> I also included the italian translation to the new package and your fix. 
>> Hopefully it is ok.
>> 
>> Cheers, 
>> tim
>> 
>> On Sun, May 17, 2015 at 03:00:24PM +0200, Thibaut Varène wrote:
>>> OK, thanks everybody.
>>> 
>>> For the records, I'm attaching source for flashybrid-0.19 and a patch from 
>>> 0.18 to this bug report. I can't upload it to the archive, but if some DD 
>>> wants to, let them be my guest.
>>> 
>>> T.
>>> 
>>> 
>> 
>> 
>> 
>> 
>> 
>> -- 
>> Tim Weippert
>> http://weiti.org - we...@weiti.org
>> GPG Fingerprint - E704 7303 6FF0 8393 ADB1  398E 67F2 94AE 5995 7DD8
> 
> -- 
> Tim Weippert
> http://weiti.org - we...@weiti.org
> GPG Fingerprint - E704 7303 6FF0 8393 ADB1  398E 67F2 94AE 5995 7DD8

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Tim Weippert]

HI, 

i prepared an NMU and try to upload it. Don't know if i'm allowed to do so ... 
will see.

I also included the italian translation to the new package and your fix. 
Hopefully it is ok.

Cheers, 
tim

On Sun, May 17, 2015 at 03:00:24PM +0200, Thibaut Varène wrote:
> OK, thanks everybody.
> 
> For the records, I'm attaching source for flashybrid-0.19 and a patch from 
> 0.18 to this bug report. I can't upload it to the archive, but if some DD 
> wants to, let them be my guest.
> 
> T.
> 
> 





-- 
Tim Weippert
http://weiti.org - we...@weiti.org
GPG Fingerprint - E704 7303 6FF0 8393 ADB1  398E 67F2 94AE 5995 7DD8

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Thibaut Varène]

OK, thanks everybody.

For the records, I'm attaching source for flashybrid-0.19 and a patch from 0.18 
to this bug report. I can't upload it to the archive, but if some DD wants to, 
let them be my guest.

T.




flashybrid_0.18-0.19.patch
Description: Binary data


flashybrid_0.19.dsc
Description: Binary data


flashybrid_0.19.tar.xz
Description: Binary data

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Stefan Blochberger]

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

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Thibaut Varène]

 Le 14 mai 2015 à 18:07, Stefan Blochberger stefan.blochber...@mail.de a 
 écrit :

 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) 
 


 But /var/run still in use ;(

See the above two lines. I suspect in Jessie, /var/run is by default a bind 
mount of /run. Try commenting it out from /etc/flashybrid/ramstore and see if 
anything breaks.

In case that wasn’t obvious, I don’t have (yet) a Jessie machine to check this 
out.

 You just have to add --make-private to all mounts in
 /etc/init.d/flashybrid

That makes sense. From the Debian Wiki it’s obvious systemd broke everything by 
overriding the kernel default for bind mounts. This comment in the bug thread 
aligns nicely with my personal opinion on the matter:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739593#97

Best,
T

--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Tim Weippert]

On Thu, May 14, 2015 at 08:09:23PM +0200, Thibaut Varène wrote:
 
  Le 14 mai 2015 à 18:07, Stefan Blochberger stefan.blochber...@mail.de a 
  écrit :
 
  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) 
  
 
 
  But /var/run still in use ;(
 
 See the above two lines. I suspect in Jessie, /var/run is by default a bind 
 mount of /run. Try commenting it out from /etc/flashybrid/ramstore and see if 
 anything breaks.
 
 In case that wasn’t obvious, I don’t have (yet) a Jessie machine to check 
 this out.

All fine, commented /var/run in ramstore and fh-sync is syncing without error.
 
  You just have to add --make-private to all mounts in
  /etc/init.d/flashybrid
 
 That makes sense. From the Debian Wiki it’s obvious systemd broke everything 
 by overriding the kernel default for bind mounts. This comment in the bug 
 thread aligns nicely with my personal opinion on the matter:
 
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739593#97

Yes, the --make-privat flag in the init script seems to resolve the problem.
I will check the system for a longer time and get my results back.

Cheers,
tim

-- 
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

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Tim Weippert]

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

-- 
Tim Weippert
http://weiti.org - we...@weiti.org
GPG Fingerprint - E704 7303 6FF0 8393 ADB1  398E 67F2 94AE 5995 7DD8

root@indoor01:~# more /etc/debian_version 
7.8

root@indoor01:~# uname -a
Linux indoor01 3.2.0-4-486 #1 Debian 3.2.68-1+deb7u1 i586 GNU/Linux

root@indoor01:~# mount | grep root
/dev/disk/by-uuid/cf1604e5-2ea0-4411-94cc-5e0eecf87185 on /ram/root.flash type 
ext4 (ro,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
tmpfs on /root type tmpfs (rw,relatime,size=122880k)

root@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=31529,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=25500k,mode=755)
/dev/disk/by-uuid/cf1604e5-2ea0-4411-94cc-5e0eecf87185 on / type ext4 
(ro,relatime,errors=remount-ro,user_xattr,barrier=1,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=93380k)
tmpfs on /ram type tmpfs (rw,relatime,size=94208k)
tmpfs 

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Stefan Blochberger]

  Original-Nachricht 
 Betreff: Bug#784890: flashybrid: Unable to Sync ramstore directories ...
 Von: Thibaut Varène vare...@debian.org
 An:
 Datum: 11.05.2015 21:15

Found at Debian Wiki... can this be relevant:
https://wiki.debian.org/systemd#Shared_bind_mounts
I have no idea if or if not...




---
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

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Stefan Blochberger]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

-  Original-Nachricht 
Betreff: Bug#784890: flashybrid: Unable to Sync ramstore directories ...
Von: Thibaut Varène vare...@debian.org
An:
Datum: 11.05.2015 21:15

 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.
 
 That would be a very valuable experiment.
 
 Best, T.
 
Any solution yet? I have the same issue oin newly installed Debian 8
and flashybrid. On my old installation with Debain 7 it was working
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iF4EAREKAAYFAlVRzZYACgkQGxEK5TguzQp/mQD+IZLDK6yBqwlAfxp4i6FWzWjN
ChJ3ZZFN5/bGsQyIUPUA/Rn+nO5uWDQfSBqLzD4c8hb617/SYQ5KBSkX7rtuQzXQ
=2Jpc
-END PGP SIGNATURE-

---
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

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Tim Weippert]

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:
 

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Thibaut Varène]

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.

That would be a very valuable experiment.

Best,
T.

--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Thibaut Varène]

On 11 mai 2015, at 08:46, Tim Weippert we...@weiti.org wrote:

 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.

ok.

 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
 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)
^ Up to this, it's fine
 tmpfs on /ram/var/lib/exim4.flash type tmpfs (rw,relatime,size=122880k)
^ But this is wrong

 /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)
^ again, that's correct
 tmpfs on /ram/var/log.flash type tmpfs (rw,relatime,size=122880k)
^ that shouldn't be there.

 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.

There's an extraneous (and wrong) mount, and I can't quite figure out where 
it's coming from.

Maybe you could try adding a -x to /etc/init.d/flashybrid first line:
#!/bin/sh -x

and then record the boot output and add it to this bug report. 
 
 When i change fh-sync to do an remount,ro,bind, no errors occures, but 
 changes weren't synced to CF also.

fh-sync isn't the culprit here. The problem lies somewhere with the init script 
and/or the way the boot sequence happens. The init script has not been changed 
so I suspect this is a nasty side effect of jessie's switch to systemd.

HTH,
T.

--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Tim Weippert]

Hi, 

On Mon, May 11, 2015 at 06:09:32PM +0200, Thibaut Varène wrote:
 
 On 11 mai 2015, at 08:46, Tim Weippert we...@weiti.org wrote:
 
  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.
 
 ok.
 
  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
  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)
 ^ Up to this, it's fine
  tmpfs on /ram/var/lib/exim4.flash type tmpfs (rw,relatime,size=122880k)
 ^ But this is wrong

Yes, these are my thoughts too.

  /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)
 ^ again, that's correct
  tmpfs on /ram/var/log.flash type tmpfs (rw,relatime,size=122880k)
 ^ that shouldn't be there.

Jep. And so on ...

 
  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.
 
 There's an extraneous (and wrong) mount, and I can't quite figure out where 
 it's coming from.
 
 Maybe you could try adding a -x to /etc/init.d/flashybrid first line:
 #!/bin/sh -x
 
 and then record the boot output and add it to this bug report. 

Attached is the output ... but i think flashybrid makes all correct, and also 
it starts at the correct place/order. I think that
the problem is the additional tmpfs mount, too. But i can say if it is an 
kernel or systemd thing ... 

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.

Cheers, 
tim

-- 
Tim Weippert
http://weiti.org - we...@weiti.org
GPG Fingerprint - E704 7303 6FF0 8393 ADB1  398E 67F2 94AE 5995 7DD8
-- Logs begin at Mon 2015-05-11 19:23:17 CEST, end at Mon 2015-05-11 19:25:52 
CEST. --
May 11 19:23:18 indoor01 flashybrid[143]: + . /lib/lsb/init-functions
May 11 19:23:18 indoor01 flashybrid[143]: + run-parts --lsbsysinit --list 
/lib/lsb/init-functions.d
May 11 19:23:18 indoor01 flashybrid[143]: + [ -r 
/lib/lsb/init-functions.d/20-left-info-blocks ]
May 11 19:23:18 indoor01 flashybrid[143]: + . 
/lib/lsb/init-functions.d/20-left-info-blocks
May 11 19:23:18 indoor01 flashybrid[143]: + [ -r 
/lib/lsb/init-functions.d/40-systemd ]
May 11 19:23:18 indoor01 flashybrid[143]: + . 
/lib/lsb/init-functions.d/40-systemd
May 11 19:23:18 indoor01 flashybrid[143]: + _use_systemctl=0
May 11 19:23:18 indoor01 flashybrid[143]: + [ -d /run/systemd/system ]
May 11 19:23:18 indoor01 flashybrid[143]: + [ -n  ]
May 11 19:23:18 indoor01 flashybrid[143]: + [ 1 -ne 1 ]
May 11 19:23:18 indoor01 flashybrid[143]: + export _SYSTEMCTL_SKIP_REDIRECT=true
May 11 19:23:18 indoor01 flashybrid[143]: + [ 0 = 1 ]
May 11 19:23:18 indoor01 flashybrid[143]: + FANCYTTY=
May 11 19:23:18 indoor01 flashybrid[143]: + [ -e /etc/lsb-base-logging.sh ]
May 11 19:23:18 indoor01 flashybrid[143]: + true
May 11 19:23:18 indoor01 flashybrid[143]: + CONFDIR=/etc/flashybrid
May 11 19:23:18 indoor01 flashybrid[143]: + [ -e /etc/flashybrid/config ]
May 11 19:23:18 indoor01 flashybrid[143]: + . /etc/flashybrid/config
May 11 19:23:18 indoor01 flashybrid[143]: + FLASHMOUNT=/
May 11 19:23:18 indoor01 flashybrid[143]: + RAMMOUNT=/ram
May 11 19:23:18 indoor01 flashybrid[143]: + FULL_CMDS=mount -o remount,rw /
May 11 19:23:18 indoor01 flashybrid[143]: + EMBED_CMDS=mount -o remount,ro /
May 11 19:23:18 indoor01 flashybrid[143]: + FLASH_MAX=120m
May 11 19:23:18 indoor01 flashybrid[143]: + ENABLED=no
May 11 19:23:18 indoor01 flashybrid[143]: + [ -e /etc/default/flashybrid ]
May 11 19:23:18 indoor01 flashybrid[143]: + . /etc/default/flashybrid
May 11 19:23:18 indoor01 flashybrid[143]: + ENABLED=yes
May 11 19:23:18 indoor01 flashybrid[143]: + VERBOSE=yes
May 11 

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Tim Weippert]

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.

I tried different things but can't get an sync to the real CF flash disk. I 
removed /etc from ramstore to be able
to deactivate flashybrid in a normal way (mountrw - systemctl disable 
flashybrid - reboot). And i changed the max RAMDISK
space ...

I think the problem is, that all ramstore directories get bind mounted twice 
and the upper layer is an bind mount to an tmpfs
in rw ... i think all syncs will be done in the tmpfs place and not in the 
underlying CF Disk.

If i add on fh-sync remount command an ,bind, i get no error upon running 
fh-sync but the syncronisation isn't reached at
CF Disk level. Maybe there is an change in the FS and Bind Mount behaviour with 
the jessie kernel/system?

If i can help in investigation of the problem, please contact me.

Cheers, 
tim

-- System Information:
Debian Release: 8.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i586)

Kernel: Linux 3.16.0-4-586
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages flashybrid depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  rsync  3.1.1-3

flashybrid recommends no packages.

flashybrid suggests no packages.

-- Configuration Files:
/etc/flashybrid/config changed:
FLASHMOUNT=/
RAMMOUNT=/ram
FULL_CMDS=mount -o remount,rw /
EMBED_CMDS=mount -o remount,ro /
FLASH_MAX=120m

/etc/flashybrid/ramstore changed:
/var/lib/exim4
/var/log
/var/run
/root
/var/spool
/var/mail


-- debconf information:
* flashybrid/remove:


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#784890: flashybrid: Unable to Sync ramstore directories ...

[Thibaut Varène]

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.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org