https://bugzilla.novell.com/show_bug.cgi?id=645793
https://bugzilla.novell.com/show_bug.cgi?id=645793#c0
Summary: file descriptor 3 (/dev/blog) leaked on vgchange invocation Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: crrodriguez@novell.com QAContact: qa@suse.de Found By: Community User Blocker: No
Created an attachment (id=394465) --> (http://bugzilla.novell.com/attachment.cgi?id=394465) screen shot of the meesage
Hi:
Looks like some process is either not close()'ing /dev/blog or it isnt opening it with O_CLOEXEC and boot ends with a warning like is shown in the attached screenshot.
https://bugzilla.novell.com/show_bug.cgi?id=645793
https://bugzilla.novell.com/show_bug.cgi?id=645793#c
Cristian Rodríguez crrodriguez@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |hare@novell.com |ovo.novell.com |
https://bugzilla.novell.com/show_bug.cgi?id=645793
https://bugzilla.novell.com/show_bug.cgi?id=645793#c1
--- Comment #1 from Dr. Werner Fink werner@novell.com 2010-10-12 16:25:10 UTC --- Just fixed liblogger of showconsole of sysvinit. Now startpar should not hand over the file descriptor anymore. Created request id 50406.
https://bugzilla.novell.com/show_bug.cgi?id=645793
https://bugzilla.novell.com/show_bug.cgi?id=645793#c2
Cristian Rodríguez crrodriguez@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Critical
--- Comment #2 from Cristian Rodríguez crrodriguez@novell.com 2010-10-12 16:38:07 CLST --- Thanks werner, that indeed fixes the "leaked fd" message but does not make lvm to shutdown cleanly yet :|
The one volume is still active at shutdown.
https://bugzilla.novell.com/show_bug.cgi?id=645793
https://bugzilla.novell.com/show_bug.cgi?id=645793#c3
Hannes Reinecke hare@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|hare@novell.com |xwhu@novell.com
--- Comment #3 from Hannes Reinecke hare@novell.com 2010-10-13 06:18:50 UTC --- None of my business. That's LVM.
https://bugzilla.novell.com/show_bug.cgi?id=645793
https://bugzilla.novell.com/show_bug.cgi?id=645793#c4
Xinwei Hu xwhu@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |crrodriguez@novell.com
--- Comment #4 from Xinwei Hu xwhu@novell.com 2010-10-13 06:28:14 UTC --- Is the volume of root ?
https://bugzilla.novell.com/show_bug.cgi?id=645793
https://bugzilla.novell.com/show_bug.cgi?id=645793#c5
Cristian Rodríguez crrodriguez@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|crrodriguez@novell.com |
--- Comment #5 from Cristian Rodríguez crrodriguez@novell.com 2010-10-13 10:23:28 CLST --- (In reply to comment #4)
Is the volume of root ?
Yes.
https://bugzilla.novell.com/show_bug.cgi?id=645793
https://bugzilla.novell.com/show_bug.cgi?id=645793#c6
Xinwei Hu xwhu@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |crrodriguez@novell.com
--- Comment #6 from Xinwei Hu xwhu@novell.com 2010-10-22 03:49:50 UTC --- If it's failed to be umount first, lvm surely cannot deactivate it. But leaveing the LV active is harmless here, cause the machine is shutting down anyway.
https://bugzilla.novell.com/show_bug.cgi?id=645793
https://bugzilla.novell.com/show_bug.cgi?id=645793#c7
--- Comment #7 from Dr. Werner Fink werner@novell.com 2010-10-22 08:43:25 UTC --- This may lead to a file system check at startup ... right?
https://bugzilla.novell.com/show_bug.cgi?id=645793
https://bugzilla.novell.com/show_bug.cgi?id=645793#c8
--- Comment #8 from Xinwei Hu xwhu@novell.com 2010-10-22 09:06:40 UTC --- (In reply to comment #7)
This may lead to a file system check at startup ... right?
I don't think so. Here's the reason, and please correct me if I am wrong.
All other file systems are umount by boot.localfs, and the / file system is remount as "ro" by halt. So by the time, all file systems are clean. And the LV itself doesn't cache data. Leaving an LV activated, won't cause data loose, and won't cause file system check at startup.
https://bugzilla.novell.com/show_bug.cgi?id=645793
https://bugzilla.novell.com/show_bug.cgi?id=645793#c
Cristian Rodríguez crrodriguez@opensuse.org changed:
What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|crrodriguez@novell.com |crrodriguez@opensuse.org
https://bugzilla.novell.com/show_bug.cgi?id=645793
https://bugzilla.novell.com/show_bug.cgi?id=645793#c
Xinwei Hu xwhu@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|xwhu@suse.com |dmzhang@suse.com
https://bugzilla.novell.com/show_bug.cgi?id=645793
https://bugzilla.novell.com/show_bug.cgi?id=645793#c9
dong mao zhang dmzhang@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED InfoProvider|crrodriguez@opensuse.org | Resolution| |NORESPONSE
--- Comment #9 from dong mao zhang dmzhang@suse.com 2012-01-02 18:05:05 UTC --- I think this bug could be closed, during the shutting down process, no data is lost from active LV while all file system are clean.
https://bugzilla.novell.com/show_bug.cgi?id=645793
https://bugzilla.novell.com/show_bug.cgi?id=645793#c10
--- Comment #10 from Cristian Rodríguez crrodriguez@opensuse.org 2012-01-03 17:04:31 CLST --- (In reply to comment #9)
I think this bug could be closed, during the shutting down process, no data is lost from active LV while all file system are clean.
Yes, and it was a problem in sysvinit.
-
bugzilla_noreply＠novell.com