All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fredrik Skog" <fredrik.skog@rodang.se>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] Called while suspended
Date: Thu, 25 Mar 2010 13:54:39 +0100	[thread overview]
Message-ID: <BCCA5923972740C7A167865BABE25FDB@caramon> (raw)
In-Reply-To: 20100319222156.GE7345@redhat.com

Hi all,

I'm in the progress of switching a WD15EADS-00P8B0 disk to a  Samsung F2 
1.5TB drive because of all the reouble associated with the WD drives 
regarding 4kb block, system freeze and poor performance.

I unmounted the VG and began doing a pvmove.

At first it went well but after 30-40% done it began complaining big time.

**** snip****

 WARNING: dev_open(/dev/hdb2) called while suspended
  WARNING: dev_open(/dev/hdb3) called while suspended
  WARNING: dev_open(/dev/hdb4) called while suspended
  /dev/sdc1: Moved: 40.8%
  WARNING: dev_open(/dev/sdc1) called while suspended
  WARNING: dev_open(/dev/hda1) called while suspended
  WARNING: dev_open(/dev/hda2) called while suspended
  WARNING: dev_open(/dev/hda3) called while suspended
  WARNING: dev_open(/dev/hda4) called while suspended
  WARNING: dev_open(/dev/sdb1) called while suspended
  WARNING: dev_open(/dev/sdd1) called while suspended
  WARNING: dev_open(/dev/sde) called while suspended
  WARNING: dev_open(/dev/hdb1) called while suspended
  WARNING: dev_open(/dev/hdb2) called while suspended
  WARNING: dev_open(/dev/hdb3) called while suspended
  WARNING: dev_open(/dev/hdb4) called while suspended
  WARNING: dev_open(/dev/sdc1) called while suspended
  WARNING: dev_open(/dev/sdc1) called while suspended
  WARNING: dev_open(/dev/hda1) called while suspended
  WARNING: dev_open(/dev/hda2) called while suspended
  WARNING: dev_open(/dev/hda3) called while suspended
  WARNING: dev_open(/dev/hda4) called while suspended
  WARNING: dev_open(/dev/sdb1) called while suspended
  WARNING: dev_open(/dev/sdb1) called while suspended
  WARNING: dev_open(/dev/sdd1) called while suspended
  WARNING: dev_open(/dev/sde) called while suspended
  WARNING: dev_open(/dev/hdb1) called while suspended
  WARNING: dev_open(/dev/hdb2) called while suspended
  WARNING: dev_open(/dev/hdb3) called while suspended
  WARNING: dev_open(/dev/hdb4) called while suspended
  WARNING: dev_open(/dev/sdc1) called while suspended
  WARNING: dev_open(/dev/hda1) called while suspended
  WARNING: dev_open(/dev/hda2) called while suspended
  WARNING: dev_open(/dev/hda3) called while suspended
  WARNING: dev_open(/dev/hda4) called while suspended
  WARNING: dev_open(/dev/sdb1) called while suspended
  WARNING: dev_open(/dev/sdd1) called while suspended
  WARNING: dev_open(/dev/sde) called while suspended
  WARNING: dev_open(/dev/hdb1) called while suspended
  WARNING: dev_open(/dev/hdb2) called while suspended
  WARNING: dev_open(/dev/hdb3) called while suspended
  WARNING: dev_open(/dev/hdb4) called while suspended
  /dev/sdc1: Moved: 40.9%
  WARNING: dev_open(/dev/sdc1) called while suspended
  WARNING: dev_open(/dev/hda1) called while suspended
  WARNING: dev_open(/dev/hda2) called while suspended

**** snip***

What is happening here and should i be worried the data will be lost? I'm 
not very good at LVM so I'm very worried right now.

Thanks for any input on this

/Fredrik Skog

  parent reply	other threads:[~2010-03-25 12:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19 18:13 [linux-lvm] Data alignment Phillip Susi
2010-03-19 18:36 ` Eugene Vilensky
2010-03-19 18:54   ` Phillip Susi
2010-03-19 19:54     ` Ray Morris
2010-03-19 21:20       ` Phillip Susi
2010-03-20  7:32     ` Luca Berra
2010-03-19 19:25 ` Mike Snitzer
2010-03-19 21:27   ` Phillip Susi
2010-03-19 22:21     ` Mike Snitzer
2010-03-19 23:11       ` Mike Snitzer
2010-03-25 12:54       ` Fredrik Skog [this message]
2010-03-20 23:02 ` Stuart D. Gathman

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=BCCA5923972740C7A167865BABE25FDB@caramon \
    --to=fredrik.skog@rodang.se \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.