I just built 2 brand new machines, fresh everything:
Gigabyte Motherboards
AMD Phenom(tm) 9850 Quad-Core Processors
Highpoint 2640x4 RAID controller w/4 seagate drives in RAID-10 configuration
1x500GB Hitachi drive for booting
1x2TB Hitachi drive for backups
I get tons of these:
and tons of these:
and a few of these:
Quite often (almost everytime the backup runs)... Now is this normal and happening just because it's cleaning up the snapshot, or is this something to be concerned about? It's happening on both servers...
Additional Information... Just checked this mornings logs and noticed this... It happens on this particular VM fairly often..
There are THOUSANDS of similar lines (the log file itself is 372MB!)... All of the other VM's backup fine with ZERO errors... This is an OpenVZ container, not a QEMU (otherwise I'd think the disk image might be bad)... Ideas? It's a fairly high-volume mailserver...
I have 16GB set aside for the snapshot, and this starts happening ~30 minutes into the backup...
Gigabyte Motherboards
AMD Phenom(tm) 9850 Quad-Core Processors
Highpoint 2640x4 RAID controller w/4 seagate drives in RAID-10 configuration
1x500GB Hitachi drive for booting
1x2TB Hitachi drive for backups
I get tons of these:
Code:
EXT4-fs error (device dm-5): __ext4_get_inode_loc: unable to read inode block - inode=13811696, block=55214592
Code:
EXT4-fs error (device dm-5): ext4_find_entry: reading directory #12730436 offset 0
Code:
EXT4-fs: mballoc: 1 blocks 1 reqs (0 success)
EXT4-fs: mballoc: 1 extents scanned, 0 goal hits, 1 2^N hits, 0 breaks, 0 lost
EXT4-fs: mballoc: 11 generated and it took 457676
EXT4-fs: mballoc: 512 preallocated, 0 discarded
ext4_abort called.
EXT4-fs error (device dm-5): ext4_put_super: Couldn't clean up the journal
EXT4-fs: barriers enabled
kjournald2 starting: pid 23341, dev dm-5:8, commit interval 5 seconds
EXT4 FS on dm-5, internal journal on dm-5:8
EXT4-fs: mballoc enabled
ext4_orphan_cleanup: deleting unreferenced inode 12592186
ext4_orphan_cleanup: deleting unreferenced inode 12553793
ext4_orphan_cleanup: deleting unreferenced inode 12553792
ext4_orphan_cleanup: deleting unreferenced inode 12553791
ext4_orphan_cleanup: deleting unreferenced inode 12550908
ext4_orphan_cleanup: deleting unreferenced inode 12550907
ext4_orphan_cleanup: deleting unreferenced inode 12435833
EXT4-fs: dm-5: 7 orphan inodes deleted
EXT4-fs: recovery complete.
EXT4-fs: mounted filesystem dm-5 with ordered data mode
EXT4-fs: mballoc: 1 blocks 1 reqs (0 success)
EXT4-fs: mballoc: 1 extents scanned, 0 goal hits, 1 2^N hits, 0 breaks, 0 lost
EXT4-fs: mballoc: 11 generated and it took 441812
EXT4-fs: mballoc: 512 preallocated, 0 discarded
EXT4-fs: barriers enabled
Additional Information... Just checked this mornings logs and noticed this... It happens on this particular VM fairly often..
Code:
Apr 09 03:19:45 INFO: tar: ./etc/postfix/main.cf.bak: Warning: Read error at byte 0, while reading 1627 bytes: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/postfix/rbl_client_exceptions.db: Warning: Read error at byte 0, while reading 3584 bytes: Input/output e
rror
Apr 09 03:19:45 INFO: tar: ./etc/postfix/master.cf: Warning: Read error at byte 0, while reading 1024 bytes: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/postfix/postfix-files: Warning: Read error at byte 0, while reading 5120 bytes: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/postfix/mysql_virtual_alias_maps.cf: Warning: Read error at byte 0, while reading 177 bytes: Input/output
error
Apr 09 03:19:45 INFO: tar: ./etc/postfix/main.cf: Warning: Read error at byte 0, while reading 2085 bytes: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/postfix/reject_over_quota.db: Warning: Read error at byte 0, while reading 1536 bytes: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/postfix/sasl/: Warning: Cannot savedir: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/postfix/sasl: Warning: Cannot close: Bad file descriptor
Apr 09 03:19:45 INFO: tar: ./etc/postfix/rbl_recipient_exceptions.db: Warning: Read error at byte 0, while reading 9216 bytes: Input/outpu
t error
Apr 09 03:19:45 INFO: tar: ./etc/postfix/virtual.db: Warning: Read error at byte 0, while reading 6144 bytes: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/postfix/post-install: Warning: Read error at byte 0, while reading 3584 bytes: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/sgml/: Warning: Cannot savedir: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/sgml: Warning: Cannot close: Bad file descriptor
Apr 09 03:19:45 INFO: tar: ./etc/sgml/catalog.old: Warning: Read error at byte 0, while reading 335 bytes: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/sgml/catalog: Warning: Read error at byte 0, while reading 366 bytes: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/sgml/xml-core.cat: Warning: Read error at byte 0, while reading 391 bytes: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/ca-certificates/: Warning: Cannot savedir: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/ca-certificates: Warning: Cannot close: Bad file descriptor
Apr 09 03:19:45 INFO: tar: ./etc/ca-certificates/update.d/: Warning: Cannot savedir: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/ca-certificates/update.d: Warning: Cannot close: Bad file descriptor
Apr 09 03:19:45 INFO: tar: ./etc/amavis/: Warning: Cannot savedir: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/amavis: Warning: Cannot close: Bad file descriptor
Apr 09 03:19:45 INFO: tar: ./etc/amavis/README.l10n: Warning: Read error at byte 0, while reading 978 bytes: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/amavis/en_US/: Warning: Cannot savedir: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/amavis/en_US: Warning: Cannot close: Bad file descriptor
Apr 09 03:19:45 INFO: tar: ./etc/amavis/en_US/template-spam-admin.txt: Warning: Read error at byte 0, while reading 1123 bytes: Input/outp
ut error
Apr 09 03:19:45 INFO: tar: ./etc/amavis/en_US/template-virus-admin.txt: Warning: Read error at byte 0, while reading 1731 bytes: Input/out
put error
Apr 09 03:19:45 INFO: tar: ./etc/amavis/en_US/template-spam-sender.txt: Warning: Read error at byte 0, while reading 1524 bytes: Input/out
put error
Apr 09 03:19:45 INFO: tar: ./etc/amavis/en_US/template-dsn.txt: Warning: Read error at byte 0, while reading 4713 bytes: Input/output erro
r
Apr 09 03:19:45 INFO: tar: ./etc/amavis/en_US/template-virus-sender.txt: Warning: Read error at byte 0, while reading 3229 bytes: Input/ou
tput error
Apr 09 03:19:45 INFO: tar: ./etc/amavis/en_US/template-virus-recipient.txt: Warning: Read error at byte 0, while reading 1543 bytes: Input
/output error
Apr 09 03:19:45 INFO: tar: ./etc/amavis/en_US/charset: Warning: Read error at byte 0, while reading 170 bytes: Input/output error
Apr 09 03:19:45 INFO: tar: ./etc/amavis/conf.d/: Warning: Cannot savedir: Input/output error
I have 16GB set aside for the snapshot, and this starts happening ~30 minutes into the backup...
Last edited: