On Tue, Jul 30, 2013 at 04:02:17PM +0200, Tom Gundersen wrote: > On Tue, Jul 30, 2013 at 2:27 PM, WANG Chao <chaow...@redhat.com> wrote: > > On 07/30/13 at 02:05pm, Tom Gundersen wrote: > >> On Tue, Jul 30, 2013 at 1:53 PM, WANG Chao <chaow...@redhat.com> wrote: > >> > - It's not before initrd-root-fs.target. > > In case of kdump, 2nd kernel initrd is used to mount non-root local/remote > > filesystem and dump vmcore there. The kdump script is running right > > before switch-root and will reboot after saving vmcore. > > > > So mounting sysroot isn't quite justified in this case. But it's still > > acceptable (since it's readonly mount), as long as it's not keeping > > systemd from reaching initrd.target (so kdump script can run later). > > If you don't have the Before=initrd-root-fs.target it means that > you'll have a race: sometimes the rootfs will be mounted before kdump > does whatever it does, and sometimes it won't. Would an option be to > not specify a root= at all in your case?
Not specifying root= is not an option as it serves as backup dump target for us. So our primary target might be send dump over network but for some reason it fails, based on user config option, we will dump core to root in /var/crash. Thanks Vivek _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
