FS#24309 - After Initscript upgrade error in mounting local filesystems tmpfs & devpts

Attached to Project: Arch Linux
Opened by ChrisVS (Strider) - Monday, 16 May 2011, 18:47 GMT
Last edited by Tom Gundersen (tomegun) - Tuesday, 17 May 2011, 18:44 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Tom Gundersen (tomegun)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

After the last upgrade to the initscripts package I receive the following error in my boot log :

mount: none already mounted or /dev/pts busy
mount: according to mtab, /dev/pts is already mounted on /dev/pts

Here is the contents of /etc/mtab :

proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
sys /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=497620,mode=755 0 0
run /run tmpfs rw,nosuid,nodev,noexec,relatime,size=10240k 0 0
/dev/mapper/vg_arch-lv_root / ext4 rw,commit=0 0 0
/dev/pts devpts rw,relatime,mode=600,ptmxmode=000 (null) 0 0
/dev/shm tmpfs rw,relatime (null) 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
none /dev/shm tmpfs rw 0 0
/dev/mapper/vg_docs-lv_home /home ext4 rw,commit=0 0 0
/dev/mapper/vg_docs-lv_music /music ext4 rw,commit=0 0 0
/dev/mapper/vg_docs-lv_pictures /pictures ext4 rw,commit=0 0 0
/dev/md3 /boot ext3 rw,commit=0 0 0
/dev/sdc2 /media/exthd-sdc2 ext3 rw,noexec,nosuid,nodev,relatime,commit=0 0 0
/dev/sdc1 /media/exthd-sdc1 fuseblk rw,noexec,nosuid,nodev,allow_other,blksize=4096 0 0
gvfs-fuse-daemon /home/chris/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,user=chris 0 0

Also when shutting down I noticed error messages for these filesystems (sometimes my PC just hangs during shutdown because of this).
When downgrading the initscripts package I do not have these problems anymore.
This task depends upon

Closed by  Tom Gundersen (tomegun)
Tuesday, 17 May 2011, 18:44 GMT
Reason for closing:  Not a bug
Additional comments about closing:  See comment by djgera.
Comment by Ionut Biru (wonder) - Monday, 16 May 2011, 19:23 GMT
do you have custom kernel?
Comment by Tom Gundersen (tomegun) - Monday, 16 May 2011, 20:08 GMT
Could you attach your boot log (/var/log/boot), and the output of dmesg just after boot?

I don't understand why you get these messages, in principle mount should just ignore the already mounted case when doing "mount -a". At boot it should be harmless, but the hanging shutdown is more worrying.

I will try a few more things to reproduce it at my end, but I have had no luck so far...
Comment by ChrisVS (Strider) - Monday, 16 May 2011, 20:18 GMT
I use the stock kernel.

Here is my /var/log/boot file attached. Also the output of dmesg (for what it's worth : I do not have the error anymore since I downgraded).
   boot (75.7 KiB)
   dmesg.out (58.4 KiB)
Comment by Gerardo Exequiel Pozzi (djgera) - Monday, 16 May 2011, 22:54 GMT
@Chris: Looks like you didn't read my answer in you forum post.

Quoting here:
Remove /dev/pts and /dev/shm from fstab or...
If you have custom options for these filesystems: put as "source" (change "none" to "devpts", and "none" -> "shm"). (New util-linux[#1] puts null string when "none" is used as source).
Do the same with all other entries with "none" as source, put any name ;)

[#1] http://mailman.archlinux.org/pipermail/arch-releng/2011-May/001736.html

Loading...