[opensuse] boot.lvm not being executed ?
I seem to remember having seen this before, but I'm not sure. On my newly upgraded 12.2 system, /etc/init.d/boot.lvm is, afaict, not being executed on startup, so all LVs remain inactive. stork1:/etc/init.d # find . -iname \*lvm\* ./boot.d/K05boot.lvm ./boot.d/S09boot.lvm ./boot.lvm When I run it manually, it works fine: stork1:/etc/init.d # ./boot.lvm start redirecting to systemctl Waiting for udev to settle... Scanning for LVM volume groups... Reading all physical volumes. This may take a while... Found volume group "xxxxxxxxx" using metadata type lvm2 Found volume group "xxxxxx" using metadata type lvm2 Activating LVM volume groups... 3 logical volume(s) in volume group "xxxxxxxxxxx" now active 5 logical volume(s) in volume group "xxxxxx" now active Before I go and open a bugreport, I was just wondering if anyone else is seeing a similar behaviour? -- Per Jessen, Zürich (22.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
I seem to remember having seen this before, but I'm not sure. On my newly upgraded 12.2 system, /etc/init.d/boot.lvm is, afaict, not being executed on startup, so all LVs remain inactive.
stork1:/etc/init.d # find . -iname \*lvm\* ./boot.d/K05boot.lvm ./boot.d/S09boot.lvm ./boot.lvm
When I run it manually, it works fine:
stork1:/etc/init.d # ./boot.lvm start redirecting to systemctl Waiting for udev to settle... Scanning for LVM volume groups... Reading all physical volumes. This may take a while... Found volume group "xxxxxxxxx" using metadata type lvm2 Found volume group "xxxxxx" using metadata type lvm2 Activating LVM volume groups... 3 logical volume(s) in volume group "xxxxxxxxxxx" now active 5 logical volume(s) in volume group "xxxxxx" now active
Before I go and open a bugreport, I was just wondering if anyone else is seeing a similar behaviour?
https://bugzilla.novell.com/show_bug.cgi?id=781417 -- Per Jessen, Zürich (10.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Per Jessen wrote:
I seem to remember having seen this before, but I'm not sure. On my newly upgraded 12.2 system, /etc/init.d/boot.lvm is, afaict, not being executed on startup, so all LVs remain inactive.
stork1:/etc/init.d # find . -iname \*lvm\* ./boot.d/K05boot.lvm ./boot.d/S09boot.lvm ./boot.lvm
When I run it manually, it works fine:
stork1:/etc/init.d # ./boot.lvm start redirecting to systemctl Waiting for udev to settle... Scanning for LVM volume groups... Reading all physical volumes. This may take a while... Found volume group "xxxxxxxxx" using metadata type lvm2 Found volume group "xxxxxx" using metadata type lvm2 Activating LVM volume groups... 3 logical volume(s) in volume group "xxxxxxxxxxx" now active 5 logical volume(s) in volume group "xxxxxx" now active
Before I go and open a bugreport, I was just wondering if anyone else is seeing a similar behaviour?
There must be others using LVM on 12.1 or 12.2? I've just rebooted a remote server, and got caught out by this issue again. I.e. the server wouldn't start because the LVM volumes couldn't be mounted. -- Per Jessen, Zürich (12.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [09-28-12 04:45]:
There must be others using LVM on 12.1 or 12.2? I've just rebooted a remote server, and got caught out by this issue again. I.e. the server wouldn't start because the LVM volumes couldn't be mounted.
I am running lvm but with a separate /boot. 12.2+Tumbleweed and see no problems. I did have some problems about a year ago but ancient mind and 300+ days have deluded memories :^( ... gud luk -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-28-12 04:45]:
There must be others using LVM on 12.1 or 12.2? I've just rebooted a remote server, and got caught out by this issue again. I.e. the server wouldn't start because the LVM volumes couldn't be mounted.
I am running lvm but with a separate /boot. 12.2+Tumbleweed and see no problems. I did have some problems about a year ago but ancient mind and 300+ days have deluded memories :^( ...
My root filesystem is also separate, I only use LVM for the data volume(s). I take it you're using systemd? -- Per Jessen, Zürich (16.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 28/09/12 10:16, Per Jessen escribió:
My root filesystem is also separate, I only use LVM for the data volume(s). I take it you're using systemd?
what does systemctl status lvm.service says ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
El 28/09/12 10:16, Per Jessen escribió:
My root filesystem is also separate, I only use LVM for the data volume(s). I take it you're using systemd?
what does systemctl status lvm.service says ?
After I ran boot.lvm manually, it looks fine - I'll reboot the systems and see what it says before that. -- Per Jessen, Zürich (16.9°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Cristian Rodríguez wrote:
El 28/09/12 10:16, Per Jessen escribió:
My root filesystem is also separate, I only use LVM for the data volume(s). I take it you're using systemd?
what does systemctl status lvm.service says ?
After I ran boot.lvm manually, it looks fine - I'll reboot the systems and see what it says before that.
Well, it looks fine: # systemctl status lvm.service lvm.service - LSB: start logical volumes Loaded: loaded (/etc/init.d/boot.lvm) Active: active (exited) since Fri, 28 Sep 2012 15:31:48 +0200; 2min 2s ago Process: 507 ExecStart=/etc/init.d/boot.lvm start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/lvm.service Sep 28 15:31:43 kzinti boot.lvm[507]: Waiting for udev to settle... Sep 28 15:31:47 kzinti boot.lvm[507]: Scanning for LVM volume groups... Sep 28 15:31:47 kzinti boot.lvm[507]: Reading all physical volumes. This may take a while... Sep 28 15:31:47 kzinti boot.lvm[507]: Found volume group "kzinti" using metadata type lvm2 Sep 28 15:31:47 kzinti boot.lvm[507]: Activating LVM volume groups... Is there any chance that something clashes between mounting all file system and starting lvm? -- Per Jessen, Zürich (17.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Well, it looks fine:
# systemctl status lvm.service lvm.service - LSB: start logical volumes Loaded: loaded (/etc/init.d/boot.lvm) Active: active (exited) since Fri, 28 Sep 2012 15:31:48 +0200; 2min 2s ago Process: 507 ExecStart=/etc/init.d/boot.lvm start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/lvm.service
Sep 28 15:31:43 kzinti boot.lvm[507]: Waiting for udev to settle... Sep 28 15:31:47 kzinti boot.lvm[507]: Scanning for LVM volume groups... Sep 28 15:31:47 kzinti boot.lvm[507]: Reading all physical volumes. This may take a while... Sep 28 15:31:47 kzinti boot.lvm[507]: Found volume group "kzinti" using metadata type lvm2 Sep 28 15:31:47 kzinti boot.lvm[507]: Activating LVM volume groups...
Is there any chance that something clashes between mounting all file system and starting lvm?
Okay, on this machine it actually seems to be working, except for these entries in fstab: /dev/kzinti/opensuse /var/opensuse ext4 defaults 0 2 The above works fine. This one doesn't - how do I make it wat for the above to become ready? /var/opensuse/openSUSE-11.0-DVD-i386.iso /srv/www/vhosts/install/htdocs/opensuse110/i386 iso9660 ro 0 2 -- Per Jessen, Zürich (17.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 28/09/12 11:27, Per Jessen escribió:
/var/opensuse/openSUSE-11.0-DVD-i386.iso /srv/www/vhosts/install/htdocs/opensuse110/i386 iso9660 ro 0 2
Isnt a DVD fstype -t udf -o loop ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
El 28/09/12 11:27, Per Jessen escribió:
/var/opensuse/openSUSE-11.0-DVD-i386.iso /srv/www/vhosts/install/htdocs/opensuse110/i386 iso9660 ro 0 2
Isnt a DVD fstype -t udf -o loop ?
It works well without when I manually run 'mount -a', but I'll try it. -- Per Jessen, Zürich (17.9°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Cristian Rodríguez wrote:
El 28/09/12 11:27, Per Jessen escribió:
/var/opensuse/openSUSE-11.0-DVD-i386.iso /srv/www/vhosts/install/htdocs/opensuse110/i386 iso9660 ro 0 2
Isnt a DVD fstype -t udf -o loop ?
It works well without when I manually run 'mount -a', but I'll try it.
Okay, I've tried it with just "ro" (my original setup) and "ro,loop", both work equally well (except at boot-time). I guess mount is being smart and realises that what is being mounted is a file? -- Per Jessen, Zürich (17.9°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 28/09/12 11:39, Per Jessen escribió:
Per Jessen wrote:
Cristian Rodríguez wrote:
El 28/09/12 11:27, Per Jessen escribió:
/var/opensuse/openSUSE-11.0-DVD-i386.iso /srv/www/vhosts/install/htdocs/opensuse110/i386 iso9660 ro 0 2
Isnt a DVD fstype -t udf -o loop ?
It works well without when I manually run 'mount -a', but I'll try it.
Okay, I've tried it with just "ro" (my original setup) and "ro,loop", both work equally well (except at boot-time). I guess mount is being smart and realises that what is being mounted is a file?
add to that line ..... noauto,comment=systemd.automount -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
El 28/09/12 11:39, Per Jessen escribió:
Per Jessen wrote:
Cristian Rodríguez wrote:
El 28/09/12 11:27, Per Jessen escribió:
/var/opensuse/openSUSE-11.0-DVD-i386.iso /srv/www/vhosts/install/htdocs/opensuse110/i386 iso9660 ro 0 2
Isnt a DVD fstype -t udf -o loop ?
It works well without when I manually run 'mount -a', but I'll try it.
Okay, I've tried it with just "ro" (my original setup) and "ro,loop", both work equally well (except at boot-time). I guess mount is being smart and realises that what is being mounted is a file?
add to that line ..... noauto,comment=systemd.automount
Hmm, I tried that - with it, the system does boot, but my DVD doesn't get loop-mounted. -- Per Jessen, Zürich (17.9°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El vie 28 sep 2012 12:05:14 CLST, Per Jessen escribió:
Cristian Rodríguez wrote:
El 28/09/12 11:39, Per Jessen escribió:
Per Jessen wrote:
Cristian Rodríguez wrote:
El 28/09/12 11:27, Per Jessen escribió:
/var/opensuse/openSUSE-11.0-DVD-i386.iso /srv/www/vhosts/install/htdocs/opensuse110/i386 iso9660 ro 0 2
Isnt a DVD fstype -t udf -o loop ?
It works well without when I manually run 'mount -a', but I'll try it.
Okay, I've tried it with just "ro" (my original setup) and "ro,loop", both work equally well (except at boot-time). I guess mount is being smart and realises that what is being mounted is a file?
add to that line ..... noauto,comment=systemd.automount
Hmm, I tried that - with it, the system does boot, but my DVD doesn't get loop-mounted.
Ok, did you tried accessing the mount point first ? and then.. what the logs say about it ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
El vie 28 sep 2012 12:05:14 CLST, Per Jessen escribió:
Cristian Rodríguez wrote:
Ok, did you tried accessing the mount point first ? and then.. what the logs say about it ?
Ah, I see what you're trying to do - no, before I had not tried accessing the mount point, so it wasn't auto-mounted, duh! However, I'm trying it now (as a plain user), and my 'ls <mtpt>' is hanging. I found this in the log: Sep 28 17:27:24 kzinti systemd[1]: Job var-opensuse-openSUSE\x2d11.0\x2dDVD\x2di386.iso.device/start timed out. Sep 28 17:27:24 kzinti systemd[1]: Job srv-www-vhosts-install-htdocs-opensuse110-i386.mount/start failed with result 'dependency'. Sep 28 17:27:24 kzinti systemd[1]: Job fsck@var-opensuse-openSUSE\x2d11.0\x2dDVD\x2di386.iso.service/start failed with result 'dependency'. Sep 28 17:27:24 kzinti systemd[1]: Job var-opensuse-openSUSE\x2d11.0\x2dDVD\x2di386.iso.device/start failed with result 'timeout'. thanks Per -- Per Jessen, Zürich (18.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 28/09/12 12:30, Per Jessen escribió:
Cristian Rodríguez wrote:
El vie 28 sep 2012 12:05:14 CLST, Per Jessen escribió:
Cristian Rodríguez wrote:
Ok, did you tried accessing the mount point first ? and then.. what the logs say about it ?
Ah, I see what you're trying to do - no, before I had not tried accessing the mount point, so it wasn't auto-mounted, duh! However, I'm trying it now (as a plain user), and my 'ls <mtpt>' is hanging. I found this in the log:
Sep 28 17:27:24 kzinti systemd[1]: Job var-opensuse-openSUSE\x2d11.0\x2dDVD\x2di386.iso.device/start timed out. Sep 28 17:27:24 kzinti systemd[1]: Job srv-www-vhosts-install-htdocs-opensuse110-i386.mount/start failed with result 'dependency'. Sep 28 17:27:24 kzinti systemd[1]: Job fsck@var-opensuse-openSUSE\x2d11.0\x2dDVD\x2di386.iso.service/start failed with result 'dependency'. Sep 28 17:27:24 kzinti systemd[1]: Job var-opensuse-openSUSE\x2d11.0\x2dDVD\x2di386.iso.device/start failed with result 'timeout'.
Hrmmm... disable fsck for the mount point.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
El 28/09/12 12:30, Per Jessen escribió:
Cristian Rodríguez wrote:
El vie 28 sep 2012 12:05:14 CLST, Per Jessen escribió:
Cristian Rodríguez wrote:
Ok, did you tried accessing the mount point first ? and then.. what the logs say about it ?
Ah, I see what you're trying to do - no, before I had not tried accessing the mount point, so it wasn't auto-mounted, duh! However, I'm trying it now (as a plain user), and my 'ls <mtpt>' is hanging. I found this in the log:
Sep 28 17:27:24 kzinti systemd[1]: Job var-opensuse-openSUSE\x2d11.0\x2dDVD\x2di386.iso.device/start timed out. Sep 28 17:27:24 kzinti systemd[1]: Job srv-www-vhosts-install-htdocs-opensuse110-i386.mount/start failed with result 'dependency'. Sep 28 17:27:24 kzinti systemd[1]: Job fsck@var-opensuse-openSUSE\x2d11.0\x2dDVD\x2di386.iso.service/start failed with result 'dependency'. Sep 28 17:27:24 kzinti systemd[1]: Job var-opensuse-openSUSE\x2d11.0\x2dDVD\x2di386.iso.device/start failed with result 'timeout'.
Hrmmm... disable fsck for the mount point..
Yeah - didn't make much difference though. Accessing the <mtpt> still hangs, but now I see nothing in the log. -- Per Jessen, Zürich (17.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 28/09/12 13:30, Per Jessen escribió:
Yeah - didn't make much difference though. Accessing the <mtpt> still hangs, but now I see nothing in the log.
does "systemctl" list the mount as failed ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
El 28/09/12 13:30, Per Jessen escribió:
Yeah - didn't make much difference though. Accessing the <mtpt> still hangs, but now I see nothing in the log.
does "systemctl" list the mount as failed ?
Nope, it says it's good: srv-www-vhosts-install-htdocs-opensuse110-i386.automount loaded active running srv-www-vhosts-install-htdocs-opensuse110-i386.automount
Just wondering, are the relevant kernel modules loaded ( loop and udf ? )
Neither one is loaded. If I do a manual mount, "nls_utf8" and "loop" get loaded. -- Per Jessen, Zürich (13.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 28/09/12 14:54, Per Jessen escribió:
Cristian Rodríguez wrote:
El 28/09/12 13:30, Per Jessen escribió:
Yeah - didn't make much difference though. Accessing the <mtpt> still hangs, but now I see nothing in the log.
does "systemctl" list the mount as failed ?
Nope, it says it's good:
srv-www-vhosts-install-htdocs-opensuse110-i386.automount loaded active running srv-www-vhosts-install-htdocs-opensuse110-i386.automount
Just wondering, are the relevant kernel modules loaded ( loop and udf ? )
Neither one is loaded.
If I do a manual mount, "nls_utf8" and "loop" get loaded.
Ok, try this. echo "loop" > /etc/modules-load.d/loop.conf and reboot. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
El 28/09/12 14:54, Per Jessen escribió:
Cristian Rodríguez wrote:
El 28/09/12 13:30, Per Jessen escribió:
Yeah - didn't make much difference though. Accessing the <mtpt> still hangs, but now I see nothing in the log.
does "systemctl" list the mount as failed ?
Nope, it says it's good:
srv-www-vhosts-install-htdocs-opensuse110-i386.automount loaded active running srv-www-vhosts-install-htdocs-opensuse110-i386.automount
Just wondering, are the relevant kernel modules loaded ( loop and udf ? )
Neither one is loaded.
If I do a manual mount, "nls_utf8" and "loop" get loaded.
Ok, try this.
echo "loop" > /etc/modules-load.d/loop.conf
and reboot.
Thanks, that did the trick. Shouldn't "loop" have been automagically loaded though? -- Per Jessen, Zürich (12.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Sep 29, 2012 at 09:59:28AM +0200, Per Jessen wrote:
Cristian Rodríguez wrote: [ 8< ]
Ok, try this.
echo "loop" > /etc/modules-load.d/loop.conf
and reboot.
Thanks, that did the trick. Shouldn't "loop" have been automagically loaded though?
No. The more modules get loaded the more memory gets used. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Lars Müller wrote:
On Sat, Sep 29, 2012 at 09:59:28AM +0200, Per Jessen wrote:
Cristian Rodríguez wrote: [ 8< ]
Ok, try this.
echo "loop" > /etc/modules-load.d/loop.conf
and reboot.
Thanks, that did the trick. Shouldn't "loop" have been automagically loaded though?
No. The more modules get loaded the more memory gets used.
Uh, Lars, "loop" was auto-loaded before when I did a "mount -o loop", so why shouldn't it be auto-loaded just because systemd now does the auto mount??? -- Per Jessen, Zürich (12.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Sep 29, 2012 at 01:16:57PM +0200, Per Jessen wrote:
Lars Müller wrote:
On Sat, Sep 29, 2012 at 09:59:28AM +0200, Per Jessen wrote:
Cristian Rodríguez wrote: [ 8< ]
Ok, try this.
echo "loop" > /etc/modules-load.d/loop.conf
and reboot.
Thanks, that did the trick. Shouldn't "loop" have been automagically loaded though?
No. The more modules get loaded the more memory gets used.
Uh, Lars, "loop" was auto-loaded before when I did a "mount -o loop", so why shouldn't it be auto-loaded just because systemd now does the auto mount???
Automatic load is ok. It was my intention to ensure the loop module doesn't get included unconditionally on every system. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On 29/09/12 04:59, Per Jessen wrote:
echo "loop" > /etc/modules-load.d/loop.conf
and reboot.
Thanks, that did the trick. Shouldn't "loop" have been automagically loaded though?
No. this is the expected behaviour.. you have to define what modules that are not in the initrd you want to load. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
On 29/09/12 04:59, Per Jessen wrote:
echo "loop" > /etc/modules-load.d/loop.conf
and reboot.
Thanks, that did the trick. Shouldn't "loop" have been automagically loaded though?
No. this is the expected behaviour.. you have to define what modules that are not in the initrd you want to load.
Really? There must be something I've misunderstood. How about "nfs_utf8" that is loaded automatically? Btw, is the ISO image also automatically unmounted? -- Per Jessen, Zürich (11.9°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 29/09/12 13:32, Per Jessen escribió:
Really? There must be something I've misunderstood. How about "nfs_utf8" that is loaded automatically?
Use the source luke ! :-) config UDF_FS tristate "UDF file system support" select CRC_ITU_T help This is the new file system used on some CD-ROMs and DVDs. Say Y if you intend to mount DVD discs or CDRW's written in packet mode, or if written to by other UDF utilities, such as DirectCD. Please read <file:Documentation/filesystems/udf.txt>. To compile this file system support as a module, choose M here: the module will be called udf. If unsure, say N. config UDF_NLS bool default y depends on (UDF_FS=m && NLS) || (UDF_FS=y && NLS=y) or config JOLIET bool "Microsoft Joliet CDROM extensions" depends on ISO9660_FS select NLS help Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system which allows for long filenames in unicode format (unicode is the new 16 bit character code, successor to ASCII, which encodes the characters of almost all languages of the world; see <http://www.unicode.org/> for more information). Say Y here if you want to be able to read Joliet CD-ROMs under Linux. Both selects or depend on NLS.. when either is loaded, the default NLS module is loaded ( this has nothing to do with boot.lvm , systemd but the kernel) So, it loads when the *filesystem* module of the source image becames known.
Btw, is the ISO image also automatically unmounted?
when the system goes down ? yes. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
El 29/09/12 13:32, Per Jessen escribió:
Really? There must be something I've misunderstood. How about "nfs_utf8" that is loaded automatically?
Use the source luke ! :-)
hehe, yeah - I'm aware of most of that, what I don't understand is: with this systemd auto-mount setup, "loop" has to be added to /etc/modules-load.d whereas with my previous setup (everything in fstab), "loop" was automatically loaded? Did mount do that behind the scenes?
Both selects or depend on NLS.. when either is loaded, the default NLS module is loaded ( this has nothing to do with boot.lvm , systemd but the kernel)
Understood.
So, it loads when the *filesystem* module of the source image becames known.
Btw, is the ISO image also automatically unmounted?
when the system goes down ? yes.
Okay, I was wondering if there was a timeout like with "regular" autofs. -- Per Jessen, Zürich (11.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 30/09/12 04:43, Per Jessen escribió:
hehe, yeah - I'm aware of most of that, what I don't understand is:
with this systemd auto-mount setup, "loop" has to be added to /etc/modules-load.d
whereas with my previous setup (everything in fstab), "loop" was automatically loaded? Did mount do that behind the scenes?
No, it was loaded by /etc/init.d/boot.localfs that is no longer used, it has never "autoloaded" ;) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
El 30/09/12 04:43, Per Jessen escribió:
hehe, yeah - I'm aware of most of that, what I don't understand is:
with this systemd auto-mount setup, "loop" has to be added to /etc/modules-load.d
whereas with my previous setup (everything in fstab), "loop" was automatically loaded? Did mount do that behind the scenes?
No, it was loaded by /etc/init.d/boot.localfs that is no longer used, it has never "autoloaded" ;)
Thanks for the explanation! -- Per Jessen, Zürich (13.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 30/09/12 11:16, Per Jessen escribió:
Thanks for the explanation!
You are welcome.. after gaining understanding of what this changes are and the rationale behind them everything starts to clear up and make sense :-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 28/09/12 13:30, Per Jessen escribió:
Yeah - didn't make much difference though. Accessing the <mtpt> still hangs, but now I see nothing in the log.
Just wondering, are the relevant kernel modules loaded ( loop and udf ? ) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Per Jessen wrote:
Well, it looks fine:
# systemctl status lvm.service lvm.service - LSB: start logical volumes Loaded: loaded (/etc/init.d/boot.lvm) Active: active (exited) since Fri, 28 Sep 2012 15:31:48 +0200; 2min 2s ago Process: 507 ExecStart=/etc/init.d/boot.lvm start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/lvm.service
Sep 28 15:31:43 kzinti boot.lvm[507]: Waiting for udev to settle... Sep 28 15:31:47 kzinti boot.lvm[507]: Scanning for LVM volume groups... Sep 28 15:31:47 kzinti boot.lvm[507]: Reading all physical volumes. This may take a while... Sep 28 15:31:47 kzinti boot.lvm[507]: Found volume group "kzinti" using metadata type lvm2 Sep 28 15:31:47 kzinti boot.lvm[507]: Activating LVM volume groups...
Another question - why don't I see the above messages in /var/log/messages? (shouldn't they be there too?). -- Per Jessen, Zürich (17.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 28/09/12 11:31, Per Jessen escribió:
Another question - why don't I see the above messages in /var/log/messages? (shouldn't they be there too?).
the journal has access to that early messages, which is what systemctl uses to read them ;) They will indeed appear later in the boot sequence in /var/log/messages -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
El 28/09/12 11:31, Per Jessen escribió:
Another question - why don't I see the above messages in /var/log/messages? (shouldn't they be there too?).
the journal has access to that early messages, which is what systemctl uses to read them ;) They will indeed appear later in the boot sequence in /var/log/messages
You mean later as in a later update? Right now, I don't see them in /var/log/messages at all. -- Per Jessen, Zürich (17.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 28/09/12 11:50, Per Jessen escribió:
Cristian Rodríguez wrote:
El 28/09/12 11:31, Per Jessen escribió:
Another question - why don't I see the above messages in /var/log/messages? (shouldn't they be there too?).
the journal has access to that early messages, which is what systemctl uses to read them ;) They will indeed appear later in the boot sequence in /var/log/messages
You mean later as in a later update?
No I didnt mean that. tghe messages may appear later if /var/log/messages is writable. however they might not, see the discussion about the journal, it has access to all those messages because it is tightly integrated into the init system. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-09-28 16:31, Per Jessen wrote:
Another question - why don't I see the above messages in /var/log/messages? (shouldn't they be there too?).
The system might be ro at the time. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBlt5YACgkQIvFNjefEBxrBTACdFVwFpDcQqjjo+4yIpc9IWCvU imkAoLkpjDohSj6whP3HE2dc6Ilbskud =w1Ei -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen <per@computer.org> [09-28-12 09:19]:
Patrick Shanahan wrote:
I am running lvm but with a separate /boot. 12.2+Tumbleweed and see no problems. I did have some problems about a year ago but ancient mind and 300+ days have deluded memories :^( ...
My root filesystem is also separate, I only use LVM for the data volume(s). I take it you're using systemd?
yes -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 2012-09-28 at 10:22 -0400, Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [09-28-12 09:19]:
Patrick Shanahan wrote:
I am running lvm but with a separate /boot. 12.2+Tumbleweed and see no problems. I did have some problems about a year ago but ancient mind and 300+ days have deluded memories :^( ... My root filesystem is also separate, I only use LVM for the data volume(s). I take it you're using systemd? yes
I'm seeing a similar problem on a new openSUSE 12.2 workstation. The system is LVM [internal SATA] and that comes up without an issue [separate /boot, everything else is LVM]. But the LVM VG on a set of USB drives is not seen at boot and can't be mounted automatically. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Adam Tauno Williams -
Carlos E. R. -
Cristian Rodríguez -
Lars Müller -
Patrick Shanahan -
Per Jessen