Re: startup: separate /var partition hoses /run, shm (shared memory)?
http://lists.debian.org/debian-user/2012/11/msg00679.html
On every startup, on the initial {black screen, white text} I get
errors beginning with
> Mount point '/run' does not exist. Skipping mount.
and ending (just before it goes to X) with many (10 > n > 100) lines
beginning with
> shm_open() failed
I suspect this is related to having a separate /var partition, since,
once the box is booted and I'm logged in, I see that
* /run is symlinked to /var/run
http://lists.debian.org/debian-user/2012/11/msg00682.html
>>> /var/run [should] be symlinked to /run. So /run should be a tmpfs
>>> and /run/shm and /run/lock part of it. Also /dev/shm should [be]
>>> symlinked to /run/shm as well. Can you post your /etc/fstab and
>>> output from 'df -hl' command?
http://lists.debian.org/debian-user/2012/11/msg00684.html
>> $ cat /etc/fstab
>> proc/proc procdefaults0 0
>> # /dev/sda3
>> UUID=81371084-8857-4621-8859-733596cf4862 /boot ext4
>> rw,errors=remount-ro0 0
>> # /dev/sda5
>> UUID=1ac01fa0-3a44-4ff9-9d9c-3634e2d7d741 swapswapsw 0
>> 0
>> # /dev/sda6
>> UUID=43f3e818-1727-4c73-bead-480a413d73df / ext4
>> rw,errors=remount-ro0 1
>> # /dev/sda7
>> UUID=e19d7759-64d9-4371-b648-fb4a7ba9882c /usrext4
>> rw,errors=remount-ro0 0
>> # /dev/sda8
>> UUID=89d00ebd-7c22-4170-8cab-9e1a1273bc70 /optext4
>> rw,errors=remount-ro0 0
>> # /dev/sda9
>> UUID=064fea46-d50f-4e9b-b88b-af430ae667e0 /varext4
>> rw,errors=remount-ro0 0
>> # /dev/sda10
>> UUID=0473c32c-5667-4725-8c7b-b9b931e81f54 /tmpext4
>> rw,errors=remount-ro0 0
>> # /dev/sda11
>> UUID=575d3851-e472-45b2-be69-db4db84fedba /home ext4
>> rw,errors=remount-ro0 0
>> $ find / -maxdepth 1 -type d | grep -ve '/$' | sort | xargs du -hls 2>
>> /dev/null
>> 9.1M/bin
>> 62M /boot
>> 684K/dev
>> 30M /etc
>> 17G /home
>> 457M/lib
>> 5.2M/lib32
>> 4.0K/lib64
>> 16K /lost+found
>> 4.0K/mnt
>> 111M/opt
>> 0 /proc
>> 4.0K/.pulse
>> 4.0K/root
>> 13M /sbin
>> 4.0K/selinux
>> 4.0K/srv
>> 0 /sys
>> 72K /tmp
>> 4.9G/usr
>> 470M/var
http://lists.debian.org/debian-user/2012/11/msg00685.html
> Do you have the initscripts package and its dependencies installed?
apparently:
$ sudo aptitude install initscripts
No packages will be installed, upgraded, or removed.
...
http://lists.debian.org/debian-user/2012/11/msg00686.html
> You're quasi running Sid
Not really: I'm running LMDE testing, which is ~all debian testing.
Your assistance is appreciated, Tom Roche
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87sj89iqxi@pobox.com
Re: startup: separate /var partition hoses /run, shm (shared memory)?
On Fri, Nov 16, 2012 at 03:22:40PM +1100, Igor Cicimov wrote: > On Fri, Nov 16, 2012 at 2:47 PM, Tom Roche wrote: > > > > > What must one do to make /run mount appropriately on startup if one has > > a separate /var partition? What I mean, why I ask: > > > > I suspect this is related to having a separate /var partition, since, > > once the box is booted and I'm logged in, I see that > > > > * /run is symlinked to /var/run > > > Since /run is meant to replace all temporary filesystems in RAM I would > expect this to be other way around, ie /var/run to be symlinked to /run. So > /run should be a tmpfs and /run/shm and /run/lock part of it. Also /dev/shm > should ne symlinked to /run/shm as well. Yes, this is correct. I'm not sure quite how Tom's system ended up with the links the wrong way around, but that's definitely something which needs fixing. One situation which can cause it is if your system was upgraded inside a chroot environment (i.e. not live), but that's unlikely. rm /run mkdir /run reboot [the scripts will fix up everything else at boot] You can move stuff around and fix up the directories and links by hand, but I wouldn't advise it since these directories all contain the state of the running system, and many of them are kept open by running services. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121116122018.gw...@codelibre.net
Re: startup: separate /var partition hoses /run, shm (shared memory)?
You're quasi running Sid, this explains that you could run into trouble. Some software does expect: spinymouse@qrc:~$ df -hl | grep run tmpfs 741M 944K 740M 1% /run none5.0M 0 5.0M 0% /run/lock none1.9G 0 1.9G 0% /run/shm none100M 16K 100M 1% /run/user But your customized Sid doesn't provide it. IMO you should switch to Debian testing or to Mint Ubuntu version, if you prefer Mint. I guess base-files is installed? Can't you copy /var to / and reinstall base-files? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121116065943.74e384f6@qrc
Re: startup: separate /var partition hoses /run, shm (shared memory)?
On Fri, Nov 16, 2012 at 4:40 PM, Tom Roche wrote:
>
> http://lists.debian.org/debian-user/2012/11/msg00679.html
> >> On every startup, on the initial {black screen, white text} I get
> >> errors beginning with
>
> >> > Mount point '/run' does not exist. Skipping mount.
>
> >> and ending (just before it goes to X) with many (10 > n > 100) lines
> >> beginning with
>
> >> > shm_open() failed
>
> >> I suspect this is related to having a separate /var partition, since,
> >> once the box is booted and I'm logged in, I see that
>
> >> * /run is symlinked to /var/run
>
> http://lists.debian.org/debian-user/2012/11/msg00682.html
> > Since /run is meant to replace all temporary filesystems in RAM
> > I would expect this to be other way around, ie
> > /var/run to be symlinked to /run. So /run should be a tmpfs and
> > /run/shm and /run/lock part of it. Also
> > /dev/shm should [be] symlinked to /run/shm as well.
> > Can you post your /etc/fstab and output from 'df -hl' command?
>
> $ cat /etc/fstab
> proc/proc procdefaults0 0
> # /dev/sda3
> UUID=81371084-8857-4621-8859-733596cf4862 /boot ext4
> rw,errors=remount-ro0 0
> # /dev/sda5
> UUID=1ac01fa0-3a44-4ff9-9d9c-3634e2d7d741 swapswapsw 0
> 0
> # /dev/sda6
> UUID=43f3e818-1727-4c73-bead-480a413d73df / ext4
> rw,errors=remount-ro0 1
> # /dev/sda7
> UUID=e19d7759-64d9-4371-b648-fb4a7ba9882c /usrext4
> rw,errors=remount-ro0 0
> # /dev/sda8
> UUID=89d00ebd-7c22-4170-8cab-9e1a1273bc70 /optext4
> rw,errors=remount-ro0 0
> # /dev/sda9
> UUID=064fea46-d50f-4e9b-b88b-af430ae667e0 /varext4
> rw,errors=remount-ro0 0
> # /dev/sda10
> UUID=0473c32c-5667-4725-8c7b-b9b931e81f54 /tmpext4
> rw,errors=remount-ro0 0
> # /dev/sda11
> UUID=575d3851-e472-45b2-be69-db4db84fedba /home ext4
> rw,errors=remount-ro0 0
>
> $ find / -maxdepth 1 -type d | grep -ve '/$' | sort | xargs du -hls 2>
> /dev/null
> 9.1M/bin
> 62M /boot
> 684K/dev
> 30M /etc
> 17G /home
> 457M/lib
> 5.2M/lib32
> 4.0K/lib64
> 16K /lost+found
> 4.0K/mnt
> 111M/opt
> 0 /proc
> 4.0K/.pulse
> 4.0K/root
> 13M /sbin
> 4.0K/selinux
> 4.0K/srv
> 0 /sys
> 72K /tmp
> 4.9G/usr
> 470M/var
>
> http://lists.debian.org/debian-user/2012/11/msg00680.html
> > Does [LMDE] still use init?
>
> $ ps aux | fgrep init
> root 1 1.7 0.0 10636 832 ?Ss 00:08 0:01 init [2]
> me3253 0.0 0.0 7772 708 pts/0S+ 00:10 0:00 fgrep init
> $ ps aux | fgrep upstart
> me3264 0.0 0.0 7740 704 pts/0S+ 00:10 0:00 fgrep
> upstart
> $ ps aux | fgrep systemd
> me3266 0.0 0.0 7740 704 pts/0S+ 00:10 0:00 fgrep
> systemd
>
> Note LMDE != "Mint": latter now comes in several versions, of which LMDE
> is one.
>
> $ lsb_release -ds
> Linux Mint Debian Edition
> $ cat /etc/debian_version
> wheezy/sid
> $ uname -rv
> 3.2.0-3-amd64 #1 SMP Thu Jun 28 09:07:26 UTC 2012
>
> Your assistance is appreciated, Tom Roche
>
Do you have the initscripts package and its dependencies installed?
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: http://lists.debian.org/87vcd6hzqd@pobox.com
>
>
Re: startup: separate /var partition hoses /run, shm (shared memory)?
http://lists.debian.org/debian-user/2012/11/msg00679.html
>> On every startup, on the initial {black screen, white text} I get
>> errors beginning with
>> > Mount point '/run' does not exist. Skipping mount.
>> and ending (just before it goes to X) with many (10 > n > 100) lines
>> beginning with
>> > shm_open() failed
>> I suspect this is related to having a separate /var partition, since,
>> once the box is booted and I'm logged in, I see that
>> * /run is symlinked to /var/run
http://lists.debian.org/debian-user/2012/11/msg00682.html
> Since /run is meant to replace all temporary filesystems in RAM
> I would expect this to be other way around, ie
> /var/run to be symlinked to /run. So /run should be a tmpfs and
> /run/shm and /run/lock part of it. Also
> /dev/shm should [be] symlinked to /run/shm as well.
> Can you post your /etc/fstab and output from 'df -hl' command?
$ cat /etc/fstab
proc/proc procdefaults0 0
# /dev/sda3
UUID=81371084-8857-4621-8859-733596cf4862 /boot ext4
rw,errors=remount-ro0 0
# /dev/sda5
UUID=1ac01fa0-3a44-4ff9-9d9c-3634e2d7d741 swapswapsw 0 0
# /dev/sda6
UUID=43f3e818-1727-4c73-bead-480a413d73df / ext4
rw,errors=remount-ro0 1
# /dev/sda7
UUID=e19d7759-64d9-4371-b648-fb4a7ba9882c /usrext4
rw,errors=remount-ro0 0
# /dev/sda8
UUID=89d00ebd-7c22-4170-8cab-9e1a1273bc70 /optext4
rw,errors=remount-ro0 0
# /dev/sda9
UUID=064fea46-d50f-4e9b-b88b-af430ae667e0 /varext4
rw,errors=remount-ro0 0
# /dev/sda10
UUID=0473c32c-5667-4725-8c7b-b9b931e81f54 /tmpext4
rw,errors=remount-ro0 0
# /dev/sda11
UUID=575d3851-e472-45b2-be69-db4db84fedba /home ext4
rw,errors=remount-ro0 0
$ find / -maxdepth 1 -type d | grep -ve '/$' | sort | xargs du -hls 2> /dev/null
9.1M/bin
62M /boot
684K/dev
30M /etc
17G /home
457M/lib
5.2M/lib32
4.0K/lib64
16K /lost+found
4.0K/mnt
111M/opt
0 /proc
4.0K/.pulse
4.0K/root
13M /sbin
4.0K/selinux
4.0K/srv
0 /sys
72K /tmp
4.9G/usr
470M/var
http://lists.debian.org/debian-user/2012/11/msg00680.html
> Does [LMDE] still use init?
$ ps aux | fgrep init
root 1 1.7 0.0 10636 832 ?Ss 00:08 0:01 init [2]
me3253 0.0 0.0 7772 708 pts/0S+ 00:10 0:00 fgrep init
$ ps aux | fgrep upstart
me3264 0.0 0.0 7740 704 pts/0S+ 00:10 0:00 fgrep upstart
$ ps aux | fgrep systemd
me3266 0.0 0.0 7740 704 pts/0S+ 00:10 0:00 fgrep systemd
Note LMDE != "Mint": latter now comes in several versions, of which LMDE
is one.
$ lsb_release -ds
Linux Mint Debian Edition
$ cat /etc/debian_version
wheezy/sid
$ uname -rv
3.2.0-3-amd64 #1 SMP Thu Jun 28 09:07:26 UTC 2012
Your assistance is appreciated, Tom Roche
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87vcd6hzqd@pobox.com
Re: startup: separate /var partition hoses /run, shm (shared memory)?
On Fri, 16 Nov 2012 15:22:40 +1100 Igor Cicimov wrote: > Since /run is meant to replace all temporary filesystems in RAM I > would expect this to be other way around, ie /var/run to be symlinked > to /run. So /run should be a tmpfs and /run/shm and /run/lock part of > it. Also /dev/shm should ne symlinked to /run/shm as well. Can you > post your /etc/fstab and output from 'df -hl' command? And it's for removable devices. /media will become /run/media/"user". However, you're right, usually there's a softlink in /var/run. Oops, I was mistaken, Ubuntu does have /run too, but not /run/media/"user", they switched to /media/"user". The issue still is, that init is neither systemd nor upstart and a transition will lead to borked systems. Even on hard censored mailing lists like the Arch general, you still read the whole day about failing systems. They don't post all friendly mails if systemd does cause issues and I got mail from a member who completely is banned from the list. Don use a rolling release or something experimental at the moment. Use pure init now or install a distro that is ready with the transition to upstart or systemd and be aware that after a switch there will be issues. On Ubuntu you have a mix of "service" and "/init.d", on Arch they drop packages that don't provide "service" thingies. How do they handle this for Mint and Debian Sid? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121116053844.67494524@qrc
Re: startup: separate /var partition hoses /run, shm (shared memory)?
On Fri, Nov 16, 2012 at 2:47 PM, Tom Roche wrote:
>
> What must one do to make /run mount appropriately on startup if one has
> a separate /var partition? What I mean, why I ask:
>
> Awhile ago, I got a new box with win7 preinstalled. I repartitioned,
> adding separate partitions for swap, /, /boot, /home, /tmp, /usr, /var
> (in addition to the win7 partition). I then installed LMDE (Linux Mint
> Debian Edition, a directly-debian-derived, rolling-release, APT-packaged
> distro). This has worked well, except for a problem at startup, whether
> after restart (i.e., warm boot) or shutdown (i.e., cold boot):
>
> On every startup, on the initial {black screen, white text} I get errors
> beginning with
>
> > Mount point '/run' does not exist. Skipping mount.
>
> and ending (just before it goes to X) with many (10 > n > 100) lines
> beginning with
>
> > shm_open() failed
>
> I suspect this is related to having a separate /var partition, since,
> once the box is booted and I'm logged in, I see that
>
> * /run is symlinked to /var/run
>
Since /run is meant to replace all temporary filesystems in RAM I would
expect this to be other way around, ie /var/run to be symlinked to /run. So
/run should be a tmpfs and /run/shm and /run/lock part of it. Also /dev/shm
should ne symlinked to /run/shm as well. Can you post your /etc/fstab and
output from 'df -hl' command?
> * /run/shm is a directory
>
> I'm wondering, how to fix this problem? E.g., can I make /var (and
> therefore /var/run) mount before whatever is trying to mount /run?
>
> If there is a better place to ask this question, please lemme know.
>
> TIA, Tom Roche
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: http://lists.debian.org/87y5i2i4zj@pobox.com
>
>
Re: startup: separate /var partition hoses /run, shm (shared memory)?
PS: > > I suspect this is related to having a separate /var partition, > > since, once the box is booted and I'm logged in, I see that Yes, it is related. A known issue for the transition. While I know this from Arch Linux I found a link in German regarding to Debian: The Germany words describe what I've suspected in my previous mail. "06.04.2011 11:27:03 Aktuell kann es bei SID-Upgrades ein wenig hakeln, da durch eine neue Version von Debianbase-files das /run-Verzeichnis in Debian eingeführt wird. Das wiederrum passt nicht zu den Initscripten und kann daher Probleme bereiten. Augen auf beim Upgrade" -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121116051955.7a5a2833@qrc
Re: startup: separate /var partition hoses /run, shm (shared memory)?
On Thu, 15 Nov 2012 22:47:12 -0500
Tom Roche wrote:
>
> What must one do to make /run mount appropriately on startup if one
> has a separate /var partition? What I mean, why I ask:
>
> Awhile ago, I got a new box with win7 preinstalled. I repartitioned,
> adding separate partitions for swap, /, /boot, /home, /tmp, /usr, /var
> (in addition to the win7 partition). I then installed LMDE (Linux Mint
> Debian Edition, a directly-debian-derived, rolling-release,
> APT-packaged distro). This has worked well, except for a problem at
> startup, whether after restart (i.e., warm boot) or shutdown (i.e.,
> cold boot):
>
> On every startup, on the initial {black screen, white text} I get
> errors beginning with
>
> > Mount point '/run' does not exist. Skipping mount.
>
> and ending (just before it goes to X) with many (10 > n > 100) lines
> beginning with
>
> > shm_open() failed
>
> I suspect this is related to having a separate /var partition, since,
> once the box is booted and I'm logged in, I see that
>
> * /run is symlinked to /var/run
> * /run/shm is a directory
>
> I'm wondering, how to fix this problem? E.g., can I make /var (and
> therefore /var/run) mount before whatever is trying to mount /run?
>
> If there is a better place to ask this question, please lemme know.
>
> TIA, Tom Roche
If the Debian version is that Debian as the Ubuntu version I once
tested was Ubuntu, then I wouldn't call it a directly-debian-derived,
but crap that has nothing to do with Debian. But to be fair, I don't
know current Mint. Btw. Debian isn't a rolling release and if Mint is
a rolling release, than I guess I understand whats going wrong. Perhaps
they simply use Debian and build own packages the way upstream tries
to force dependencies. So you might use init, but systemd already is
installed too, or perhaps they mix it with Ubuntu, upstart.
At the moment there are several ways for startup and for the filesystem
hierarchy used by different distros. The package maintainers have to
fix upstream dependencies to the distro specific needs.
I've got issues with major distros regarding to "innovations". I
suspect that such a smal distro with such a small community, less
testers and bug reports must fail.
"Run" even isn't used by latest Ubuntu. It's used by Fedora and Arch,
both use systemd instead of init.
I only have an outdated AV Linux, really a Debian stable with less
customization and I don't know the current state of Debian, but I
suspect the filesystem hierarchy today sill is the same.
Again, I suspect that the Mint file hierarchy is equal to Debian, but
some Mint packages are simply build directly from upstream and don't
fit to this hierarchy.
Does Mint still use init?
Regards,
Ralf
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121116050816.6f0f2cfa@qrc
