Исходное сообщение
"Для файловой системы Ext4 представлена поддержка шифрования" Отправлено pavel_simple, 14-Апр-15 20:51
>[оверквотинг удален] > #mount /dev/nbd0p1 /nbd0/ > #cd /nbd0/ && tar -cf www.tgz var/www/ > EXT3-fs (nbd0p1): 5 orphan inodes deleted > EXT3-fs (nbd0p1): recovery complete > EXT3-fs (nbd0p1): mounted filesystem with ordered data mode > nbd (pid 117717: qemu-nbd) got signal 9 > УСЁ. Для системы это теперь "Buffer I/O error on device dm-3", со > стороны lvm - любая операция _намертво_ блокируется попыткой прочитать из device > mapper'а. > Данный пример дёрнул из debian 6.0.7 + proxmox. эмммм... proxmox использует сильно специфичное ядро вот например debian wheeze + backport # uname -srv Linux 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.7-ckt7-1~bpo70+1 (2015-04-07) modprobe nbd  max_part=63 qemu-nbd -c /dev/nbd0 test.img fdisk /dev/nbd0 ls -la /dev/nbd0p1 brw-rw---T 1 root disk 43, 1 Apr 14 22:28 /dev/nbd0p1 mkfs.ext4 /dev/nbd0p1 mount /dev/nbd0p1 /mnt/ cd /mnt/ dd if=/dev/urandom of=/mnt/test.file bs=1k count=100 cat >>test.file <<EOF печатаем либерду и одновременно kill -KILL на qemu-nbd EOF -su: test.file: Read-only file system dmesg [10047.450190] nbd: registered device at major 43 [10091.031143]  nbd0: unknown partition table [10108.135157]  nbd0: p1 [10130.033100] block nbd0: Other side returned error (22) [10130.033112] end_request: I/O error, dev nbd0, sector 34816 [10152.637827] EXT4-fs (nbd0p1): mounted filesystem with ordered data mode. Opts: (null) [10273.090016] nbd (pid 4693: qemu-nbd) got signal 9 [10273.090032] block nbd0: shutting down socket [10273.090043] block nbd0: Receive control failed (result -4) [10273.090148] block nbd0: queue cleared [10274.763185] block nbd0: Attempted send on closed socket [10274.763198] end_request: I/O error, dev nbd0, sector 61704 [10274.763242] block nbd0: Attempted send on closed socket [10274.763247] end_request: I/O error, dev nbd0, sector 61960 [10274.763270] block nbd0: Attempted send on closed socket [10274.763274] end_request: I/O error, dev nbd0, sector 62216 [10274.763296] block nbd0: Attempted send on closed socket [10274.763299] end_request: I/O error, dev nbd0, sector 62472 [10274.763320] block nbd0: Attempted send on closed socket [10274.763324] end_request: I/O error, dev nbd0, sector 62728 [10274.763345] block nbd0: Attempted send on closed socket [10274.763349] end_request: I/O error, dev nbd0, sector 62984 [10274.763370] block nbd0: Attempted send on closed socket [10274.763374] end_request: I/O error, dev nbd0, sector 63240 [10274.763395] block nbd0: Attempted send on closed socket [10274.763398] end_request: I/O error, dev nbd0, sector 63496 [10274.763419] block nbd0: Attempted send on closed socket [10274.763423] end_request: I/O error, dev nbd0, sector 63752 [10274.763444] block nbd0: Attempted send on closed socket [10274.763448] end_request: I/O error, dev nbd0, sector 64008 [10274.763469] block nbd0: Attempted send on closed socket [10274.763490] block nbd0: Attempted send on closed socket [10274.763512] block nbd0: Attempted send on closed socket [10274.763533] block nbd0: Attempted send on closed socket [10274.763554] block nbd0: Attempted send on closed socket [10274.763575] block nbd0: Attempted send on closed socket [10280.100946] block nbd0: Attempted send on closed socket [10280.100962] blk_update_request: 6 callbacks suppressed [10280.100968] end_request: I/O error, dev nbd0, sector 3672472 [10280.100978] Aborting journal on device nbd0p1-8. [10280.101001] block nbd0: Attempted send on closed socket [10280.101005] end_request: I/O error, dev nbd0, sector 3672064 [10280.101011] Buffer I/O error on device nbd0p1, logical block 458752 [10280.101015] lost page write due to I/O error on nbd0p1 [10280.101041] JBD2: Error -5 detected when updating journal superblock for nbd0p1-8. [10281.715909] block nbd0: Attempted send on closed socket [10281.715920] end_request: I/O error, dev nbd0, sector 2048 [10281.715927] Buffer I/O error on device nbd0p1, logical block 0 [10281.715931] lost page write due to I/O error on nbd0p1 [10281.715966] EXT4-fs error (device nbd0p1): ext4_journal_check_start:56: Detected aborted journal [10281.715973] EXT4-fs (nbd0p1): Remounting filesystem read-only [10281.715978] EXT4-fs (nbd0p1): previous I/O error to superblock detected [10281.715993] block nbd0: Attempted send on closed socket [10281.715997] end_request: I/O error, dev nbd0, sector 2048 [10281.716001] Buffer I/O error on device nbd0p1, logical block 0 [10281.716005] lost page write due to I/O error on nbd0p1 # pvs   /dev/nbd0p1: read failed after 0 of 4096 at 4293853184: Input/output error   /dev/nbd0p1: read failed after 0 of 4096 at 4293910528: Input/output error   /dev/nbd0p1: read failed after 0 of 4096 at 0: Input/output error   /dev/nbd0p1: read failed after 0 of 4096 at 4096: Input/output error   PV         VG     Fmt  Attr PSize   PFree   /dev/sda5  ***    lvm2 a--  295.52g 4.08g   /dev/sdc3  ***    lvm2 a--  111.82g    0   /dev/sdc5  ***    lvm2 a--   52.52g 1.37g # lvs   /dev/nbd0p1: read failed after 0 of 4096 at 4293853184: Input/output error   /dev/nbd0p1: read failed after 0 of 4096 at 4293910528: Input/output error   /dev/nbd0p1: read failed after 0 of 4096 at 0: Input/output error   /dev/nbd0p1: read failed after 0 of 4096 at 4096: Input/output error   LV          VG     Attr     LSize   Pool Origin Data%  Move Log Copy%  Convert   ***      ***    -wi-ao-- 136.97g                                             ***      ***    -wi-a---  14.00g                                             ***      ***    -wi-ao--  12.00g                                             ***      ***    -wi-ao-- 281.43g                                             ***      ***    -wi-ao--  10.00g                                           # lvcreate -n asd -L 4M *** mkfs.ext4 /dev/mapper/***-asd mkdir /tmp/asd mount /dev/mapper/***-asd /tmp/asd/ cd /tmp/asd echo 1> test.file cd - umount /tmp/asd/ lvremove /dev/***/asd   /dev/nbd0p1: read failed after 0 of 4096 at 4293853184: Input/output error   /dev/nbd0p1: read failed after 0 of 4096 at 4293910528: Input/output error   /dev/nbd0p1: read failed after 0 of 4096 at 0: Input/output error   /dev/nbd0p1: read failed after 0 of 4096 at 4096: Input/output error Do you really want to remove active logical volume asd? [y/n]: y   Logical volume "asd" successfully removed qemu-nbd -c /dev/nbd0 test.img mount -o remount,rw /mnt/ mount: cannot remount block device /dev/nbd0p1 read-write, is write-protected # blockdev --setrw /dev/nbd0 # blockdev --setrw /dev/nbd0p1 # mount -o remount,rw /mnt/ mount: cannot remount block device /dev/nbd0p1 read-write, is write-protected что собственно логично. НО никакого лока на nbd у lvm нет, или нет уже, а то ядро которое идёт с proxmox'ом оставляет много лучшего, как и сама система  (proxmox) в целом. (чего только стоит распад кластера при недоступности удалённой fs (например nfs))

Ваше сообщение
Имя*:
EMail:	Для отправки ответов на email укажите знак ! перед адресом, например, !user@host.ru (!! - не показывать email). Более тонкая настройка отправки ответов производится в профиле зарегистрированного участника форума.
Заголовок*:
Сообщение*:	>>[оверквотинг удален] >> #mount /dev/nbd0p1 /nbd0/ >> #cd /nbd0/ && tar -cf www.tgz var/www/ >> EXT3-fs (nbd0p1): 5 orphan inodes deleted >> EXT3-fs (nbd0p1): recovery complete >> EXT3-fs (nbd0p1): mounted filesystem with ordered data mode >> nbd (pid 117717: qemu-nbd) got signal 9 >> УСЁ. Для системы это теперь "Buffer I/O error on device dm-3", со >> стороны lvm - любая операция _намертво_ блокируется попыткой прочитать из device >> mapper'а. >> Данный пример дёрнул из debian 6.0.7 + proxmox. > эмммм... proxmox использует сильно специфичное ядро > вот например debian wheeze + backport > # uname -srv > Linux 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.7-ckt7-1~bpo70+1 (2015-04-07) > modprobe nbd max_part=63 > qemu-nbd -c /dev/nbd0 test.img > fdisk /dev/nbd0 > ls -la /dev/nbd0p1 > brw-rw---T 1 root disk 43, 1 Apr 14 22:28 /dev/nbd0p1 > mkfs.ext4 /dev/nbd0p1 > mount /dev/nbd0p1 /mnt/ > cd /mnt/ > dd if=/dev/urandom of=/mnt/test.file bs=1k count=100 > cat >>test.file <<EOF > печатаем либерду и одновременно kill -KILL на qemu-nbd > EOF > -su: test.file: Read-only file system > dmesg > [10047.450190] nbd: registered device at major 43 > [10091.031143] nbd0: unknown partition table > [10108.135157] nbd0: p1 > [10130.033100] block nbd0: Other side returned error (22) > [10130.033112] end_request: I/O error, dev nbd0, sector 34816 > [10152.637827] EXT4-fs (nbd0p1): mounted filesystem with ordered data mode. Opts: (null) > [10273.090016] nbd (pid 4693: qemu-nbd) got signal 9 > [10273.090032] block nbd0: shutting down socket > [10273.090043] block nbd0: Receive control failed (result -4) > [10273.090148] block nbd0: queue cleared > [10274.763185] block nbd0: Attempted send on closed socket > [10274.763198] end_request: I/O error, dev nbd0, sector 61704 > [10274.763242] block nbd0: Attempted send on closed socket > [10274.763247] end_request: I/O error, dev nbd0, sector 61960 > [10274.763270] block nbd0: Attempted send on closed socket > [10274.763274] end_request: I/O error, dev nbd0, sector 62216 > [10274.763296] block nbd0: Attempted send on closed socket > [10274.763299] end_request: I/O error, dev nbd0, sector 62472 > [10274.763320] block nbd0: Attempted send on closed socket > [10274.763324] end_request: I/O error, dev nbd0, sector 62728 > [10274.763345] block nbd0: Attempted send on closed socket > [10274.763349] end_request: I/O error, dev nbd0, sector 62984 > [10274.763370] block nbd0: Attempted send on closed socket > [10274.763374] end_request: I/O error, dev nbd0, sector 63240 > [10274.763395] block nbd0: Attempted send on closed socket > [10274.763398] end_request: I/O error, dev nbd0, sector 63496 > [10274.763419] block nbd0: Attempted send on closed socket > [10274.763423] end_request: I/O error, dev nbd0, sector 63752 > [10274.763444] block nbd0: Attempted send on closed socket > [10274.763448] end_request: I/O error, dev nbd0, sector 64008 > [10274.763469] block nbd0: Attempted send on closed socket > [10274.763490] block nbd0: Attempted send on closed socket > [10274.763512] block nbd0: Attempted send on closed socket > [10274.763533] block nbd0: Attempted send on closed socket > [10274.763554] block nbd0: Attempted send on closed socket > [10274.763575] block nbd0: Attempted send on closed socket > [10280.100946] block nbd0: Attempted send on closed socket > [10280.100962] blk_update_request: 6 callbacks suppressed > [10280.100968] end_request: I/O error, dev nbd0, sector 3672472 > [10280.100978] Aborting journal on device nbd0p1-8. > [10280.101001] block nbd0: Attempted send on closed socket > [10280.101005] end_request: I/O error, dev nbd0, sector 3672064 > [10280.101011] Buffer I/O error on device nbd0p1, logical block 458752 > [10280.101015] lost page write due to I/O error on nbd0p1 > [10280.101041] JBD2: Error -5 detected when updating journal superblock for nbd0p1-8. > [10281.715909] block nbd0: Attempted send on closed socket > [10281.715920] end_request: I/O error, dev nbd0, sector 2048 > [10281.715927] Buffer I/O error on device nbd0p1, logical block 0 > [10281.715931] lost page write due to I/O error on nbd0p1 > [10281.715966] EXT4-fs error (device nbd0p1): ext4_journal_check_start:56: Detected > aborted journal > [10281.715973] EXT4-fs (nbd0p1): Remounting filesystem read-only > [10281.715978] EXT4-fs (nbd0p1): previous I/O error to superblock detected > [10281.715993] block nbd0: Attempted send on closed socket > [10281.715997] end_request: I/O error, dev nbd0, sector 2048 > [10281.716001] Buffer I/O error on device nbd0p1, logical block 0 > [10281.716005] lost page write due to I/O error on nbd0p1 > # pvs > /dev/nbd0p1: read failed after 0 of 4096 at 4293853184: Input/output > error > /dev/nbd0p1: read failed after 0 of 4096 at 4293910528: Input/output > error > /dev/nbd0p1: read failed after 0 of 4096 at 0: Input/output > error > /dev/nbd0p1: read failed after 0 of 4096 at 4096: Input/output > error > PV VG > Fmt Attr PSize PFree > /dev/sda5 *** lvm2 a-- 295.52g > 4.08g > /dev/sdc3 *** lvm2 a-- 111.82g > 0 > /dev/sdc5 *** lvm2 a-- > 52.52g 1.37g > # lvs > /dev/nbd0p1: read failed after 0 of 4096 at 4293853184: Input/output > error > /dev/nbd0p1: read failed after 0 of 4096 at 4293910528: Input/output > error > /dev/nbd0p1: read failed after 0 of 4096 at 0: Input/output > error > /dev/nbd0p1: read failed after 0 of 4096 at 4096: Input/output > error > LV > VG Attr LSize > Pool Origin Data% Move Log Copy% Convert > *** *** > -wi-ao-- 136.97g > *** *** > -wi-a--- 14.00g > *** *** > -wi-ao-- 12.00g > *** *** > -wi-ao-- 281.43g > *** *** > -wi-ao-- 10.00g > # lvcreate -n asd -L 4M *** > mkfs.ext4 /dev/mapper/***-asd > mkdir /tmp/asd > mount /dev/mapper/***-asd /tmp/asd/ > cd /tmp/asd > echo 1> test.file > cd - > umount /tmp/asd/ > lvremove /dev/***/asd > /dev/nbd0p1: read failed after 0 of 4096 at 4293853184: Input/output > error > /dev/nbd0p1: read failed after 0 of 4096 at 4293910528: Input/output > error > /dev/nbd0p1: read failed after 0 of 4096 at 0: Input/output > error > /dev/nbd0p1: read failed after 0 of 4096 at 4096: Input/output > error > Do you really want to remove active logical volume asd? [y/n]: y > Logical volume "asd" successfully removed > qemu-nbd -c /dev/nbd0 test.img > mount -o remount,rw /mnt/ > mount: cannot remount block device /dev/nbd0p1 read-write, is write-protected > # blockdev --setrw /dev/nbd0 > # blockdev --setrw /dev/nbd0p1 > # mount -o remount,rw /mnt/ > mount: cannot remount block device /dev/nbd0p1 read-write, is write-protected > что собственно логично. > НО никакого лока на nbd у lvm нет, или нет уже, а > то ядро которое идёт с proxmox'ом оставляет много лучшего, как и > сама система (proxmox) в целом. (чего только стоит распад кластера > при недоступности удалённой fs (например nfs))
	Введите код, изображенный на картинке: