Quote:
Originally Posted by szboardstretcher
What is the output of:
Code:
file archive.tar.xz
and can you do a:
Code:
xzcat archive.tar.xz > archive.tar
without error? |
See requested output below
Code:
root@host:/home/user# file archive.tar.xz
archive.tar.xz: data
root@host:/home/user# xzcat archive.tar.xz > archive.tar
xzcat: archive.tar.xz: Datei Format nicht erkannt
I may have some info on why the corruption happened. The archiving was done through a cronjob which runs at 11pm. I found the following in /var/log/messages:
Code:
Mar 17 23:41:20 host kernel: [25521.939579] Out of memory: Kill process 3067 (java) score 53 or sacrifice child
Mar 17 23:41:20 host kernel: [25521.939596] Killed process 3067 (java) total-vm:1212484kB, anon-rss:13856kB, file-rss:0kB
Mar 17 23:42:47 host kernel: [25610.167962] xz invoked oom-killer: gfp_mask=0x280da, order=0, oom_adj=0, oom_score_adj=0
Mar 17 23:42:47 host kernel: [25610.167966] xz cpuset=/ mems_allowed=0
Mar 17 23:42:47 host kernel: [25610.167969] Pid: 6635, comm: xz Tainted: G O 3.2.0-4-amd64 #1 Debian 3.2.54-2
Mar 17 23:42:47 host kernel: [25610.167971] Call Trace:
Mar 17 23:42:47 host kernel: [25610.167978] [<ffffffff810b742a>] ? dump_header+0x78/0x1bd
Mar 17 23:42:47 host kernel: [25610.167983] [<ffffffff8134fdc7>] ? _raw_spin_unlock_irqrestore+0xe/0xf
Mar 17 23:42:47 host kernel: [25610.167987] [<ffffffff81097dce>] ? delayacct_end+0x72/0x7d
Mar 17 23:42:47 host kernel: [25610.167991] [<ffffffff81164a56>] ? security_real_capable_noaudit+0x40/0x4f
Mar 17 23:42:47 host kernel: [25610.167994] [<ffffffff8134fdc7>] ? _raw_spin_unlock_irqrestore+0xe/0xf
Mar 17 23:42:47 host kernel: [25610.167996] [<ffffffff810b77f3>] ? oom_kill_process+0x49/0x271
Mar 17 23:42:47 host kernel: [25610.167999] [<ffffffff810b7eee>] ? out_of_memory+0x2ea/0x337
Mar 17 23:42:47 host kernel: [25610.168003] [<ffffffff810bbb85>] ? __alloc_pages_nodemask+0x629/0x7aa
Mar 17 23:42:47 host kernel: [25610.168006] [<ffffffff811aeeba>] ? radix_tree_delete+0xc0/0x1d6
Mar 17 23:42:47 host kernel: [25610.168011] [<ffffffff810e65ed>] ? alloc_pages_vma+0x12d/0x136
Mar 17 23:42:47 host kernel: [25610.168015] [<ffffffff810d1194>] ? handle_pte_fault+0x165/0x79f
Mar 17 23:42:47 host kernel: [25610.168018] [<ffffffff810ce7d5>] ? set_pmd+0x5/0x8
Mar 17 23:42:47 host kernel: [25610.168021] [<ffffffff810ce865>] ? pte_offset_kernel+0x16/0x35
Mar 17 23:42:47 host kernel: [25610.168025] [<ffffffff81352d2e>] ? do_page_fault+0x320/0x345
Mar 17 23:42:47 host kernel: [25610.168029] [<ffffffff8100d750>] ? __switch_to+0x1e5/0x258
Mar 17 23:42:47 host kernel: [25610.168033] [<ffffffff810fab68>] ? vfs_read+0xb8/0xe6
Mar 17 23:42:47 host kernel: [25610.168036] [<ffffffff81350335>] ? page_fault+0x25/0x30
Mar 17 23:42:47 host kernel: [25610.168038] Mem-Info:
Mar 17 23:42:47 host kernel: [25610.168039] Node 0 DMA per-cpu:
Mar 17 23:42:47 host kernel: [25610.168041] CPU 0: hi: 0, btch: 1 usd: 0
So it seems the process ran out of memory while archiving? The part I don't understand is that the archive has a timestamp of 14:03pm
Code:
root@host:/var/backups/entwickler# ls -halt
insgesamt 388M
drwxr-xr-x 3 root root 4,0K Mär 19 13:21 ..
drwxr-xr-x 3 root root 4,0K Mär 19 13:07 .
-rw-r--r-- 1 root root 389M Mär 18 14:03 archive.tar.xz
-rw-r--r-- 1 root root 31 Feb 17 18:23 dirlist.txt
The machine might have been rebooted somewhere in that timeframe yesterday...
