From: sverre stoltenberg <sverrest@opera.com>
To: ceph-devel@vger.kernel.org
Subject: Truncated file on posix mount
Date: Fri, 15 Jun 2012 11:43:41 +0200 [thread overview]
Message-ID: <4FDB03CD.5010202@opera.com> (raw)
I have a ceph posix mount for openstack instances, and have found some
of my kernels truncated. It looks rather random, and I have not found a
way to reproduce it, but it will happen from time to time with normal use.
the 5e...aa checksum is the correct one.
root@t06-16:/var/lib/nova/instances# md5sum */kernel
3e0a48130ddb8bfe88239df05c073a0b instance-00000001/kernel
5e9463bd77757a3889a1d9758b2b94aa instance-0000000f/kernel
5e9463bd77757a3889a1d9758b2b94aa instance-00000010/kernel
5e9463bd77757a3889a1d9758b2b94aa instance-00000011/kernel
5e9463bd77757a3889a1d9758b2b94aa instance-00000012/kernel
5e9463bd77757a3889a1d9758b2b94aa instance-00000013/kernel
3e0a48130ddb8bfe88239df05c073a0b instance-00000014/kernel
root@t06-16:/var/lib/nova/instances/instance-00000001# stat kernel
File: `kernel'
Size: 2097152 Blocks: 4096 IO Block: 4194304 regular file
Device: 0h/0d Inode: 1099511627899 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 109/libvirt-qemu) Gid: ( 111/ kvm)
Access: 2012-06-13 11:56:56.462433802 +0200
Modify: 2012-06-04 11:47:17.730781000 +0200
Change: 2012-06-04 11:47:17.730781000 +0200
Birth: -
root@t06-16:/var/lib/nova/instances/instance-00000010# stat kernel
File: `kernel'
Size: 2424448 Blocks: 4736 IO Block: 4194304 regular file
Device: 0h/0d Inode: 1099511627989 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 109/libvirt-qemu) Gid: ( 111/ kvm)
Access: 2012-06-13 09:44:03.779892491 +0200
Modify: 2012-06-13 09:43:47.178125000 +0200
Change: 2012-06-13 09:44:00.020102878 +0200
Birth: -
--
/S.
next reply other threads:[~2012-06-15 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 9:43 sverre stoltenberg [this message]
2012-06-15 11:32 ` Truncated file on posix mount Wido den Hollander
2012-06-15 12:55 ` sverre stoltenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FDB03CD.5010202@opera.com \
--to=sverrest@opera.com \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox