"
If the snapshot logical volume becomes full it will be dropped (become unusable) so it is vitally important to allocate enough space. The amount of space necessary is dependent on the usage of the snapshot, so there is no set recipe to follow for this. If the snapshot size equals the origin size, it will never overflow. |
But my box was crashed in this scenario.
Was wondering why didn't it disable the snapshots.
The underlying processor is MIPS and linux kernel version is 2.6.18.
After delving little bit in the sources I found that break is occurring while blowing away the snapshot facility -- so it`s not surprising that snapshots do not work anymore. Just before the error, kcopyd_client_destroy is called -- so that`s it for kcopyd jobs -- hence snapshots. The snapshot faciltiy is gone at that point, with or without the BUG_ON. The error actually occurs while freeing the exception tables in the slab cache.
Any pointers if this has been resolved?
I am working with lvm version 2.02.28. and device mapper version 1.02.22
Here is the log
Ending XFS recovery on filesystem: dm-1 (logdev: internal)
xfs_force_shutdown(dm-1,0x1) called from line 424 of file fs/xfs/xfs_rw.c.
Return address = 0x80302d7c
Filesystem "dm-1": I/O Error Detected. Shutting down filesystem: dm-1
Please umount the filesystem, and rectify the problem(s)
xfs_force_shutdown(dm-1,0x1) called from line 424 of file fs/xfs/xfs_rw.c.
Return address = 0x80302d7c
Buffer I/O error on device dm-1, logical block 2097024
Buffer I/O error on device dm-1, logical block 2097025
Buffer I/O error on device dm-1, logical block 2097026
Buffer I/O error on device dm-1, logical block 2097027
Buffer I/O error on device dm-1, logical block 2097028
Buffer I/O error on device dm-1, logical block 2097029
Buffer I/O error on device dm-1, logical block 2097030
Buffer I/O error on device dm-1, logical block 2097031
Buffer I/O error on device dm-1, logical block 2097024
Buffer I/O error on device dm-1, logical block 2097025
xfs_force_shutdown(dm-1,0x1) called from line 424 of file fs/xfs/xfs_rw.c.
Return address = 0x80302d7c
xfs_force_shutdown(dm-1,0x1) called from line 424 of file fs/xfs/xfs_rw.c.
Return address = 0x80302d7c
xfs_force_shutdown(dm-1,0x1) called from line 424 of file fs/xfs/xfs_rw.c.
Return address = 0x80302d7c
xfs_force_shutdown(dm-1,0x1) called from line 424 of file fs/xfs/xfs_rw.c.
Return address = 0x80302d7c
Break instruction in kernel code[#1]:
Cpu 0
$ 0 : 00000000 805d0000 00000000 812e2bc0
$ 4 : 816032c0 816032c0 9004e000 ffff00fe
$ 8 : 98c35fe0 0000e000 00000000 9f7b8000
$12 : 9bc2ad88 8051ba34 0000000a 00000002
$16 : c009d000 00000000 9715ee48 9d12a1c8
$20 : 00000200 816032c0 00000000 7f94cc60
$24 : ffffffff 00000004
$28 : 98c34000 98c35da0 00000000 803f4dbc
Hi : 0000000d
Lo : 70a3d716
epc : 8016a1f0 kmem_cache_free+0x60/0xec Not tainted
ra : 803f4dbc exit_exception_table+0x58/0xa0
Status: 9004e003 KERNEL EXL IE
Cause : 00000024
PrId : 000034c1
Modules linked in: aes bonding block2mtd
Process lvremove (pid: 31393, threadinfo=98c34000, task=9f5c6628)
Stack : 9d12a180 c009b020 00000001 c003b000 c009d000 00000000 00000000 803f4dbc
00000000 00000000 9d12a180 c009b020 9d12a180 c009b020 00000001 c003b000
100345d0 1002c7b8 803f5588 803f5570 00000000 8011df80 803edcd4 00000000
c009b020 9bc33e80 803ecdb0 00000000 9bc33e80 9d12a580 00000000 c003b000
9d12a580 9bc33e80 00000000 803ece6c 9ba67a00 9d12a580 9d12a580 9bc33e80
...
Call Trace:
[<8016a1f0>] kmem_cache_free+0x60/0xec
[<803f4dbc>] exit_exception_table+0x58/0xa0
[<803f5588>] snapshot_dtr+0x38/0x88
[<803ecdb0>] table_destroy+0x68/0xcc
[<803ece6c>] dm_table_put+0x38/0x44
[<803ec05c>] dm_put+0xac/0xc8
[<803f0200>] dev_remove+0xbc/0xe0
[<803f1460>] ctl_ioctl+0xf8/0x164
[<80183320>] do_ioctl+0x60/0x74
[<80183690>] vfs_ioctl+0x1e0/0x200
[<80183700>] sys_ioctl+0x50/0x90
[<8010c040>] stack_done+0x20/0x3c
Got a little couch potato?
Check out fun summer activities for kids.
_______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
