On Tue, 22.02.11 02:49, Alexey Shabalin (a.shaba...@gmail.com) wrote:
> 22.02.2011, в 2:10, Miklos Vajna написал(а):
>
> > On Mon, Feb 21, 2011 at 06:47:43PM +0300, Alexey Shabalin
> > wrote:
> >> systemd+udev can't replace rc.sysinit(or external script like
> >> fedora-storage-init) now. :(
>
On Wed, Feb 23, 2011 at 7:49 PM, Miklos Vajna wrote:
> On Tue, Feb 22, 2011 at 02:17:02PM +0300, Alexey Shabalin
> wrote:
>> >> For replace rc.sysinit, may be make like rc.sysinit:
>> >> first run multipath, second mdadm, and last lvm services.
>> >
>> > That is exactly what fedora-storage-init
On Tue, Feb 22, 2011 at 02:17:02PM +0300, Alexey Shabalin
wrote:
> >> For replace rc.sysinit, may be make like rc.sysinit:
> >> first run multipath, second mdadm, and last lvm services.
> >
> > That is exactly what fedora-storage-init does. Why not simply use it then?
> > :)
> >
> Yes, did so.
>
systemd+udev can't replace rc.sysinit(or external script like
fedora-storage-init) now. :(
>>>
>>> For the second case, can you see if this patch:
>>>
>>> http://article.gmane.org/gmane.linux.lvm.devel/6138
>>>
>>> helps for you?
>> Ok, I will test this. Thank you.
>>>
>>> It replaces the
On Tue, Feb 22, 2011 at 2:49 AM, Alexey Shabalin wrote:
> 22.02.2011, в 2:10, Miklos Vajna написал(а):
>
>> On Mon, Feb 21, 2011 at 06:47:43PM +0300, Alexey Shabalin
>> wrote:
>>> systemd+udev can't replace rc.sysinit(or external script like
>>> fedora-storage-init) now. :(
>>
>> For the second
22.02.2011, в 2:10, Miklos Vajna написал(а):
> On Mon, Feb 21, 2011 at 06:47:43PM +0300, Alexey Shabalin
> wrote:
>> systemd+udev can't replace rc.sysinit(or external script like
>> fedora-storage-init) now. :(
>
> For the second case, can you see if this patch:
>
> http://article.gmane.org/gma
On Mon, Feb 21, 2011 at 06:47:43PM +0300, Alexey Shabalin
wrote:
> systemd+udev can't replace rc.sysinit(or external script like
> fedora-storage-init) now. :(
For the second case, can you see if this patch:
http://article.gmane.org/gmane.linux.lvm.devel/6138
helps for you?
It replaces the la
>> >> You can see in log:
>> >> Feb 16 16:04:51 host-29 kernel: [ 11.636564] Adding 524284k swap on
>> >> /dev/mapper/VG1-Swap. Priority:-1 extents:1 across:524284k
>> >> Feb 16 16:04:51 host-29 kernel: [ 11.669141] clock[1954]: Setting
>> >> system clock (localtime): succeeded
>> >> Feb 16 16
On Fri, Feb 18, 2011 at 12:39 PM, Lennart Poettering
wrote:
> Well, maybe syncing it to local-fs is not necessary, but we probably
> want to sync it to basic.target at least. Mounts are not the only users
> of block devices, so a later service might want to use it and hence we
> should make sure t
On Fri, 18.02.11 14:24, Andrey Borzenkov (arvidj...@mail.ru) wrote:
> > I have the same question about the different fsck services. They
> > should clearly be Before=*.mount, but wouldn't it be better if they
> > were not Before=local-fs.service?
> >
>
> Makes sense for the same reason. local-fs
On Fri, 18.02.11 12:02, Tom Gundersen (t...@jklm.no) wrote:
>
> A little nitpick/question:
>
> On Fri, Feb 18, 2011 at 1:37 AM, Miklos Vajna wrote:
> > [Unit]
> > Description=LVM activation
> > DefaultDependencies=no
> > After=udev-settle.service
> > Before=local-fs.target
>
> Is the Before=lo
On Fri, Feb 18, 2011 at 2:02 PM, Tom Gundersen wrote:
> A little nitpick/question:
>
> On Fri, Feb 18, 2011 at 1:37 AM, Miklos Vajna wrote:
>> [Unit]
>> Description=LVM activation
>> DefaultDependencies=no
>> After=udev-settle.service
>> Before=local-fs.target
>
> Is the Before=local-fs.target re
A little nitpick/question:
On Fri, Feb 18, 2011 at 1:37 AM, Miklos Vajna wrote:
> [Unit]
> Description=LVM activation
> DefaultDependencies=no
> After=udev-settle.service
> Before=local-fs.target
Is the Before=local-fs.target really necessary?
Any mounts that will reside on the lvm will already
On Fri, 18.02.11 01:37, Miklos Vajna (vmik...@frugalware.org) wrote:
> On Thu, Feb 17, 2011 at 07:07:26PM +0300, Alexey Shabalin
> wrote:
> > But i have not some rule with "vgchange -a y", and have lv-disk as "LV
> > Status not available"
>
> Here is what we use at the moment:
>
> [Unit]
> Des
On Fri, Feb 18, 2011 at 3:37 AM, Miklos Vajna wrote:
> On Thu, Feb 17, 2011 at 07:07:26PM +0300, Alexey Shabalin
> wrote:
>> But i have not some rule with "vgchange -a y", and have lv-disk as "LV
>> Status not available"
>
> Here is what we use at the moment:
>
> [Unit]
> Description=LVM activat
On Thu, Feb 17, 2011 at 07:07:26PM +0300, Alexey Shabalin
wrote:
> But i have not some rule with "vgchange -a y", and have lv-disk as "LV
> Status not available"
Here is what we use at the moment:
[Unit]
Description=LVM activation
DefaultDependencies=no
After=udev-settle.service
Before=local-fs
>> >> I know that swap on lvm no good practics, but need foolproof.
>> >
>> > If you use LVM make sure to use a new version that properly installs its
>> > udev rules.
>> I used lvm-2.02.84. I don't see udev rules that run "vgchange -a y".
> Well, ensure you have /lib/udev/rules.d/11-dm-lvm.rules i
On Thu, 17.02.11 18:25, Alexey Shabalin (a.shaba...@gmail.com) wrote:
>
> On Wed, Feb 16, 2011 at 8:57 PM, Lennart Poettering wrote:
> > On Wed, 16.02.11 17:37, Alexey Shabalin wrote:
> >
> >> You can see in log:
> >> Feb 16 16:04:51 host-29 kernel: [ 11.636564] Adding 524284k swap on
> >> /de
On Wed, Feb 16, 2011 at 8:57 PM, Lennart Poettering wrote:
> On Wed, 16.02.11 17:37, Alexey Shabalin wrote:
>
>> You can see in log:
>> Feb 16 16:04:51 host-29 kernel: [ 11.636564] Adding 524284k swap on
>> /dev/mapper/VG1-Swap. Priority:-1 extents:1 across:524284k
>> Feb 16 16:04:51 host-29 ke
On Wed, 16.02.11 17:37, Alexey Shabalin (a.shaba...@gmail.com) wrote:
> You can see in log:
> Feb 16 16:04:51 host-29 kernel: [ 11.636564] Adding 524284k swap on
> /dev/mapper/VG1-Swap. Priority:-1 extents:1 across:524284k
> Feb 16 16:04:51 host-29 kernel: [ 11.669141] clock[1954]: Setting
>
On Wed, Feb 16, 2011 at 5:37 PM, Alexey Shabalin wrote:
> You can see in log:
> Feb 16 16:04:51 host-29 kernel: [ 11.636564] Adding 524284k swap on
> /dev/mapper/VG1-Swap. Priority:-1 extents:1 across:524284k
> Feb 16 16:04:51 host-29 kernel: [ 11.669141] clock[1954]: Setting
> system clock (
You can see in log:
Feb 16 16:04:51 host-29 kernel: [ 11.636564] Adding 524284k swap on
/dev/mapper/VG1-Swap. Priority:-1 extents:1 across:524284k
Feb 16 16:04:51 host-29 kernel: [ 11.669141] clock[1954]: Setting
system clock (localtime): succeeded
Feb 16 16:04:51 host-29 kernel: [ 11.770936
22 matches
Mail list logo