Bug 715883

Summary:	fsck should start before udev auto-mounting rules are applied
Product:	[openSUSE] openSUSE 11.4	Reporter:	Ilya Chernykh <anixx>
Component:	Basesystem	Assignee:	E-mail List <bnc-team-screening>
Status:	VERIFIED NORESPONSE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Factory
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Ilya Chernykh 2011-09-04 14:43:54 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.9.1.19) Gecko/20110420 SUSE/2.0.14-0.2.1 SeaMonkey/2.0.14

On each boot on my system fsck complains that the device /dev/sdc1 is busy and throws me into filesystem recovery console.

I think this is because udev auto-mounting rules as specified in sysconfig package (and which call udevmountd mounter) become applied before fsck is called (and as such the device is already mounted by the time fsck is called). 

I think fsck should be called before the udev auto-mounter can be enabled.



Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1 Ilya Chernykh 2011-09-04 14:49:07 UTC

Well may be I am the only man who encountered this because udevmountd is broken in openSUSE (see this bugreport https://bugzilla.novell.com/show_bug.cgi?id=712485 ), and I changed call to udevmountd to call to mount directly. Thus the rules which usually do not work became working and enabled before fsck test.

Still this bugreport is valid because if udevmountd gets repaired, not only me but all users withh face the same problem.

Comment 2 Greg Kroah-Hartman 2011-11-10 22:05:50 UTC

Is this still an issue on 12.1?

Comment 3 Ilya Chernykh 2011-11-10 22:52:33 UTC

I will test this in 12.1 once I upgraded to it.

Meanwhile some details.

If in the recovery console manually unmount the device and promptly run fsck, it works well, but if to unmount and wait 4-5 seconds, and then run fsck, it again complains that device is busy.

In KDE3 I utilized a workaround - a resident "devmon" script that makes automounting when HAL is unavailable. But I think the proper solution should be automounting done with udev rules, so that no resident service occupy memory other than udev.

Comment 4 Ilya Chernykh 2011-11-10 22:54:50 UTC

If fsck is passed and the sustem is booted with udev automounting rules, then automounting works well and KDE3 requires neither HAL nor devmon to automatically detect removable devices and prompt user's action.

Comment 5 Greg Kroah-Hartman 2011-12-01 18:07:02 UTC

Ok, this isn't a udev issue, reassigning...

Comment 6 Kun Kun Zhang 2012-03-08 04:46:30 UTC

Long time no response.So closed.Feel free to reopen it.Thanks.