linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Full DRDB device on LVM is now unusable
Date: Thu, 30 Jan 2014 12:01:54 +0100	[thread overview]
Message-ID: <52EA3122.2090605@redhat.com> (raw)
In-Reply-To: <26083-1390999499-900991@sneakemail.com>

Dne 29.1.2014 13:45, Seb A napsal(a):
> Write Protect appears to be off here (Thanks Angel):
>
> [root@Openfiler2 ~]# grep -i "Write Protect" /var/log/messages
> kern.info<6>: Jan 28 17:28:11 Openfiler2 kernel: Write protecting the kernel
> read-only data: 7056k
> kern.notice<5>: Jan 28 17:28:11 Openfiler2 kernel: sd 0:0:0:0: [sda] Write
> Protect is off
> kern.notice<5>: Jan 28 17:28:11 Openfiler2 kernel: sd 0:0:1:0: [sdb] Write
> Protect is off
> kern.notice<5>: Jan 28 17:28:11 Openfiler2 kernel: sd 0:0:2:0: [sdc] Write
> Protect is off
>
> Kind regards,
>
> Seb A
>
>
>
>

As a follow-up of irc discussion.


incorrect  filter rules were set.


For drbd its mandatory to let lvm2 command see only those devices which are 
supposed to be used.

Reference to drbd lvm nesting guide:
http://www.drbd.org/users-guide-8.3/s-nested-lvm.html

Rule #1 - set an appropriate 'filter' is very important.

For activation of nested LV  lvm must not see drbd origin nodes!


Zdenek

  reply	other threads:[~2014-01-30 11:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28 22:54 [linux-lvm] Full DRDB device on LVM is now unusable Seb A
2014-01-29 12:15 ` Seb A
2014-01-29 12:45   ` Seb A
2014-01-30 11:01     ` Zdenek Kabelac [this message]
2014-02-05 17:11       ` Seb A
2014-02-05 21:48         ` Lars Ellenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52EA3122.2090605@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).