mountall keeps on running

Bug #567964 reported by las
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
mountall (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: mountall

whenever a disk check happen maountall keeps on running even after login in .It uses around 60% of cpu. no error msg was given.
This is when i run top in terminal

  347 root 20 0 15748 13m 888 R 61.7 1.5 5:38.90 mountall

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: mountall 2.13
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Apr 21 21:48:38 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100215)
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: mountall

Revision history for this message
las (bandara-ls) wrote :
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Please strace this running process, e.g.

  sudo strace -p 347

(where 347 is the PID from ps)

Attach a sample of the output

Changed in mountall (Ubuntu):
status: New → Incomplete
importance: Undecided → Medium
Revision history for this message
Loïc Minier (lool) wrote :

strace output:
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(2, "mountall: Plymouth command faile"..., 34) = 34
write(11, "U\2<fsck:/home:79:Checking disk %"..., 63) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(2, "mountall: Plymouth command faile"..., 34) = 34
write(11, "U\2<fsck:/home:79:Checking disk %"..., 63) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(2, "mountall: Plymouth command faile"..., 34) = 34
write(11, "U\2<fsck:/home:79:Checking disk %"..., 63) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(2, "mountall: Plymouth command faile"..., 34) = 34
write(11, "U\2<fsck:/home:79:Checking disk %"..., 63) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(2, "mountall: Plymouth command faile"..., 34) = 34

Revision history for this message
Loïc Minier (lool) wrote :

somewhat later:
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(2, "mountall: Plymouth command faile"..., 34) = 34
write(11, "U\2<fsck:/home:90:Checking disk %"..., 63) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(2, "mountall: Plymouth command faile"..., 34) = 34
write(11, "U\2<fsck:/home:90:Checking disk %"..., 63) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(2, "mountall: Plymouth command faile"..., 34) = 34
write(11, "U\2<fsck:/home:90:Checking disk %"..., 63) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(2, "mountall: Plymouth command faile"..., 34) = 34
write(11, "U\2<fsck:/home:90:Checking disk %"..., 63) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(2, "mountall: Plymouth command faile"..., 34) = 34
write(11, "U\2<fsck:/home:90:Checking disk %"..., 63) = -1 EPIPE (Broken pipe)

Revision history for this message
Loïc Minier (lool) wrote :

There is no fsck process running anymore at this point:
root 332 98.0 1.3 76484 51924 ? R 09:37 25:23 mountall --daemon
(no child in ps fauxwww output)

Revision history for this message
Loïc Minier (lool) wrote :

(and no plymouth either obviously :)

Changed in mountall (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Martin (agima) wrote :

I noticed the same thing just now: my disk was checked and at about 60% progress the plymouth screen suddenly disappeared and the boot sequence continued. I assume that fsck died away for whatever reason...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.