ALT Linux sysadmins discussion
 help / color / mirror / Atom feed
From: Олег <ulug1@mail.ru>
To: Sysadmins@lists.altlinux.org
Subject: [Sysadmins] ошибка при переносе LVM Срочно нужна помощь
Date: Thu, 30 Oct 2008 12:00:07 +0300
Message-ID: <E1KvTNv-000PXn-00.ulug1-mail-ru@f213.mail.ru> (raw)

Добрый день!

Менял диски на более емкие на файл-сервере. массив рейд5 из четырех дисков и 2 диска на рейд средствами линукс. Добавил в LVM 2 диска - 1Тб и 500Гб, чтобы перенести на них данные и потом, вставив новые диски,  создать новый рейд и перенести на них. 
Ошибка и часть ресурсов недоступна.
Помогите срочно, пожалуйста. Боюсь неправильными действиями усугубить.
Данных 1,2Тб. Сделал для диска 1Тб:
pvmove -i 10 /dev/sde:0-238465 /dev/sdd1
перенеслось все нормально - 100%.
pvmove -i 10 /dev/sde:238466-357539 /dev/sdс1
File descriptor 3 left open
File descriptor 5 left open
File descriptor 7 left open
  device-mapper: create ioctl failed: Device or resource busy
  device-mapper: reload ioctl failed: Invalid argument
  WARNING: dev_open(/dev/sde) called while suspended
  WARNING: dev_open(/dev/sde) called while suspended
  WARNING: dev_open(/dev/sde) called while suspended
  WARNING: dev_open(/dev/sdc1) called while suspended
  WARNING: dev_open(/dev/sdd1) called while suspended
  WARNING: dev_open(/dev/sde) called while suspended
  WARNING: dev_open(/dev/sdc1) called while suspended
  WARNING: dev_open(/dev/sdd1) called while suspended
  WARNING: dev_open(/dev/sdc1) called while suspended
  WARNING: dev_open(/dev/sde) called while suspended
  WARNING: dev_open(/dev/sdd1) called while suspended
  WARNING: dev_open(/dev/sdd1) called while suspended
  WARNING: dev_open(/dev/sde) called while suspended
  WARNING: dev_open(/dev/sdc1) called while suspended
  WARNING: dev_open(/dev/sde) called while suspended
  WARNING: dev_open(/dev/sdc1) called while suspended
  WARNING: dev_open(/dev/sdd1) called while suspended
  /dev/sde: Moved: 100.0%
  device-mapper: create ioctl failed: Device or resource busy
  Unable to reactivate logical volume "pvmove0"

Устройства:
ARRAY /dev/md0 level=raid1 - /boot type ext2
ARRAY /dev/md1 level=raid1 - / type ext3
/dev/mapper/vg1-lvm0 on /mnt/raid0 type ext3 
/dev/mapper/vg5-lvm5 on /mnt/raid5 type ext3
теперь:
pvdisplay -m
PV Name               /dev/sde
Total PE              357596
Free PE               357596

PV Name               /dev/sdc1
Total PE              119234
Allocated PE          119074

cat/proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdb3[0] sda3[1]
      15358016 blocks [2/2] [UU]
md0 : active raid1 sdb1[0] sda1[1]
      305088 blocks [2/2] [UU]
ошибки в логах(kernel/errors):
Oct 30 08:08:08 fs kernel: device-mapper: table: 253:0: linear: dm-linear: Device lookup failed
Oct 30 08:34:33 fs kernel: EXT3-fs error (device dm-0): ext3_xattr_block_get: inode 118032385: bad block 248790387
Oct 30 08:34:33 fs kernel: Aborting journal on device dm-0.
Oct 30 08:34:33 fs kernel: EXT3-fs error (device dm-0): ext3_xattr_block_get: inode 118032385: bad block 248790387
Oct 30 08:34:36 fs last message repeated 41 times
Oct 30 09:01:21 fs kernel: EXT3-fs error (device dm-0): htree_dirblock_to_tree: bad entry in directory #130285584: rec_len is smaller than minimal - offset=0,
 inode=0, rec_len=0, name_len=0
Oct 30 09:01:21 fs last message repeated 4 times
Oct 30 09:01:21 fs kernel: EXT3-fs error (device dm-0): ext3_xattr_block_get: inode 97812482: bad block 252969479
Oct 30 09:01:21 fs last message repeated 2 times
Oct 30 09:01:34 fs kernel: EXT3-fs error (device dm-0): htree_dirblock_to_tree: bad entry in directory #130285584: rec_len is smaller than minimal - offset=0,
 inode=0, rec_len=0, name_len=0
Oct 30 09:01:34 fs last message repeated 23 times
Oct 30 09:04:54 fs kernel: EXT3-fs error (device dm-0): htree_dirblock_to_tree: bad entry in directory #130285584: rec_len is smaller than minimal - offset=0,
 inode=0, rec_len=0, name_len=0...
kernel/warnings:
Oct 30 08:08:08 fs kernel: device-mapper: ioctl: error adding target to table
Oct 30 11:19:38 fs kernel:
Oct 30 11:19:38 fs kernel: Call Trace:
Oct 30 11:19:38 fs kernel:  [<ffffffff80266337>] show_trace+0x34/0x47
Oct 30 11:19:38 fs kernel:  [<ffffffff8026635c>] dump_stack+0x12/0x17
Oct 30 11:19:38 fs kernel:  [<ffffffff802a8ff0>] softlockup_tick+0xdb/0xed
Oct 30 11:19:38 fs kernel:  [<ffffffff8028a7e0>] update_process_times+0x42/0x68
Oct 30 11:19:38 fs kernel:  [<ffffffff80270019>] smp_local_timer_interrupt+0x23/0x47
Oct 30 11:19:38 fs kernel:  [<ffffffff802706fc>] smp_apic_timer_interrupt+0x41/0x47
Oct 30 11:19:38 fs kernel:  [<ffffffff80259f4a>] apic_timer_interrupt+0x66/0x6c
Oct 30 11:19:38 fs kernel: DWARF2 unwinder stuck at apic_timer_interrupt+0x66/0x6c
Oct 30 11:19:38 fs kernel: Leftover inexact backtrace:
Oct 30 11:19:38 fs kernel:  <IRQ>  <EOI>  [<ffffffff8810ed76>] :ext3:ext3_find_entry+0x19d/0x58a
Oct 30 11:19:38 fs kernel:  [<ffffffff8810ed4f>] :ext3:ext3_find_entry+0x176/0x58a
Oct 30 11:19:38 fs kernel:  [<ffffffff880ec0a2>] :mbcache:__mb_cache_entry_forget+0x5d/0x65
Oct 30 11:19:38 fs kernel:  [<ffffffff80220aae>] __up_read+0x13/0x8a
Oct 30 11:19:38 fs kernel:  [<ffffffff88117778>] :ext3:ext3_xattr_get+0x21e/0x22f
Oct 30 11:19:38 fs kernel:  [<ffffffff881107fd>] :ext3:ext3_lookup+0x31/0xf3
Oct 30 11:19:38 fs kernel:  [<ffffffff8020c4d2>] do_lookup+0xc4/0x173
Oct 30 11:19:38 fs kernel:  [<ffffffff80209c7d>] __link_path_walk+0x9f0/0xf31
Oct 30 11:19:38 fs kernel:  [<ffffffff8020de33>] link_path_walk+0x5c/0xe5
Oct 30 11:19:38 fs kernel:  [<ffffffff8020c28e>] do_path_lookup+0x270/0x2ec
Oct 30 11:19:38 fs kernel:  [<ffffffff80210bdc>] getname+0x15b/0x1c1
Oct 30 11:19:38 fs kernel:  [<ffffffff8022229a>] __user_walk_fd+0x37/0x4c
Oct 30 11:19:38 fs kernel:  [<ffffffff80227042>] vfs_stat_fd+0x1b/0x4a
Oct 30 11:19:38 fs kernel:  [<ffffffff80221fa8>] sys_newstat+0x19/0x31
Oct 30 11:19:38 fs kernel:  [<ffffffff802593d6>] system_call+0x7e/0x83



             reply	other threads:[~2008-10-30  9:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30  9:00 Олег [this message]
2008-10-30  9:05 ` oleg
2008-10-30  9:45   ` Владимир
2008-10-30 15:20     ` oleg
2008-10-31  7:57       ` Владимир
2008-10-31  9:45         ` oleg
2008-10-31 10:59           ` Владимир
2008-10-30 15:52     ` oleg
2008-10-30 16:06       ` Sergey Vlasov
2008-10-30 16:44         ` oleg

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=E1KvTNv-000PXn-00.ulug1-mail-ru@f213.mail.ru \
    --to=ulug1@mail.ru \
    --cc=Sysadmins@lists.altlinux.org \
    /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

ALT Linux sysadmins discussion

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/sysadmins/0 sysadmins/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 sysadmins sysadmins/ http://lore.altlinux.org/sysadmins \
		sysadmins@lists.altlinux.org sysadmins@lists.altlinux.ru sysadmins@lists.altlinux.com
	public-inbox-index sysadmins

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.sysadmins


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git