From: "Jörg Stephan" <ml@johestephan.de>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Lvm Strange Problem
Date: Mon, 11 Oct 2010 16:23:24 +0200 [thread overview]
Message-ID: <4CB31DDC.5040206@johestephan.de> (raw)
In-Reply-To: <Pine.LNX.4.64.1010110918570.25121@bmsred.bmsi.com>
> I believe your problem is with your SAN, not LVM (you did mention using iSCSI).
> I'm talking about SAN snapshots, not LVM snapshots (although the SAN server
> could very well use LVM underneath). The SAN volumes have no names, just
> LUNs. At boot, they are searched for a matching UUID, just like directly
> attached physical volumes. When taking a SAN snapshot (clone), the UUID
> of the clone is the same as the original, whether a filesystem or VG is
> on the SAN LUN.
>
>
Okay, but we dont use SAN snapshots, we use an lvcreate --snapshot on
the client. So the storage just dont know about them.
What happens is, we lv snapshot a volume, mount it copy the data to the
new volume we create after snapshooting the source, remove the old
snapshot and turning of the new machine. It rans about half an year,
gets stoped, and after it turning on again the lvm data on the iscsi
volume is last cahnged on the 23 februar 2010, even if the snapshot was
made much earlier.
Greets
next prev parent reply other threads:[~2010-10-11 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 7:53 [linux-lvm] Lvm Strange Problem Jörg Stephan
2010-10-11 12:40 ` Stuart D. Gathman
2010-10-11 12:59 ` Jörg Stephan
2010-10-11 13:23 ` Stuart D. Gathman
2010-10-11 14:23 ` Jörg Stephan [this message]
2010-10-11 21:39 ` Stuart D. Gathman
2010-10-11 13:12 ` Stuart D. Gathman
-- strict thread matches above, loose matches on Subject: below --
2010-10-11 17:41 beswars
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=4CB31DDC.5040206@johestephan.de \
--to=ml@johestephan.de \
--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).