[PVE-User] Error LVM Snapshots

Franc Rodriguez franc.rodriguez at tecob.com
Mon Jul 21 11:23:13 CEST 2014


Hello,

Yes, some dumps fails:

Jul 21 00:46:05 px2 kernel: device-mapper: snapshots: Invalidating
snapshot: Unable to all
ocate exception.
Jul 21 00:46:08 px2 kernel: journal_bmap: journal block not found at
offset 6156 on dm-2
Jul 21 00:46:08 px2 kernel: Aborting journal on device dm-2.
Jul 21 00:46:08 px2 kernel: Buffer I/O error on device dm-2, logical
block 253854210
Jul 21 00:46:08 px2 kernel: EXT3-fs (dm-2): error:
ext3_journal_start_sb: Detected aborted
 journal
Jul 21 00:46:08 px2 kernel: EXT3-fs (dm-2): error: remounting filesystem
read-only
Jul 21 00:46:08 px2 kernel: lost page write due to I/O error on dm-2
Jul 21 00:46:08 px2 kernel: JBD: I/O error detected when updating
journal superblock for d
m-2.
Jul 21 00:46:08 px2 kernel: __journal_remove_journal_head: freeing
b_frozen_data
Jul 21 00:46:08 px2 kernel: __journal_remove_journal_head: freeing
b_frozen_data
Jul 21 00:46:08 px2 kernel: __journal_remove_journal_head: freeing
b_frozen_data
Jul 21 00:46:08 px2 kernel: __journal_remove_journal_head: freeing
b_frozen_data
Jul 21 00:46:23 px2 kernel: Buffer I/O error on device dm-2, logical
block 108101647
Jul 21 00:46:23 px2 kernel: lost page write due to I/O error on dm-2
Jul 21 00:46:23 px2 kernel: Buffer I/O error on device dm-2, logical
block 116097033
Jul 21 00:46:23 px2 kernel: lost page write due to I/O error on dm-2
Jul 21 00:46:23 px2 kernel: Buffer I/O error on device dm-2, logical
block 116097034
Jul 21 00:46:23 px2 kernel: lost page write due to I/O error on dm-2
Jul 21 00:46:23 px2 kernel: Buffer I/O error on device dm-2, logical
block 116097035
Jul 21 00:46:31 px2 kernel: EXT3-fs (dm-2): error: ext3_put_super:
Couldn't clean up the journal
Jul 21 00:46:31 px2 vzdump[675387]: ERROR: Backup of VM 506 failed -
command '(cd /mnt/vzsnap0/private/506;find . '(' -regex '^\.$' ')' -o
'(' -type 's' -prune ')' -o -print0|sed 's/\\/\\\\/g'|tar cpf - --totals
--sparse --numeric-owner --no-recursion --one-file-system --null -T
-|lzop) >/backup/dump/vzdump-openvz-506-2014_07_21-00_43_15.tar.dat'
failed: exit code 2





On 07/21/2014 10:58 AM, Dietmar Maurer wrote:
>> The dump dir is a LVM partition called backup with 1TB and I run vzdump
>> job with the command:
>>
>> vzdump --maxfiles 1 --compress lzo --mode snapshot --storage backup
>> --size 8192 -all
>>
>> syslog register some errors:
>>
>> Jul 21 09:37:04 px1 vzdump[292803]: INFO: starting new backup job:
>> vzdump 161
>> Jul 21 09:37:05 px1 vzdump[292803]: INFO: Starting Backup of VM 161
>> (openvz)
>> Jul 21 09:37:05 px1 kernel: EXT3-fs: barriers disabled
>> Jul 21 09:37:05 px1 kernel: kjournald starting.  Commit interval 5 seconds
>> Jul 21 09:37:05 px1 kernel: EXT3-fs (dm-2): using internal journal
>> Jul 21 09:37:05 px1 kernel: ext3_orphan_cleanup: deleting unreferenced
>> inode 1718856
>> [.....]
>> Jul 21 09:37:07 px1 kernel: ext3_orphan_cleanup: deleting unreferenced
>> inode 120966237
>> Jul 21 09:37:07 px1 kernel: EXT3-fs (dm-2): 389 orphan inodes deleted
>> Jul 21 09:37:07 px1 kernel: EXT3-fs (dm-2): recovery complete
>> Jul 21 09:37:07 px1 kernel: EXT3-fs (dm-2): mounted filesystem with
>> ordered data mode
>>
>> Maybe there is a problem with kernel version (2.6.32-30-pve)?
>> Someone can advise me?
> 
> What is the problem? Does the backup task fail?
> 



More information about the pve-user mailing list