On Fri, Aug 08, 2014 at 06:05:27PM +0200, Marcin Wolcendorf wrote:
> On Mon, Aug 04, 2014 at 10:48:28PM -0400, Theodore Ts'o wrote:
> > That being said, I'm pretty sure the problem will evaporate once we
> > move it to a raw image file --- the short write is something which is
> > fundamental to the block device, not the file system image.
>
> OK, so you suggest I report this bug to the kernel mainainters?
Well, the problem is we can't seem to come up with a simple
reproduction case. Also, if this isn't a bleeding edge / mainline
kernel, LKML isn't probably going to be able to help you. And I'm not
sure what the Debian maintainers would do without a reproduction case.
> But you have also said that you use the O_EXCL option. Maybe this casues some
> problems? Is it safe (assuming nothing else uses the block device) to remove
> this option and try without it?
Well, it's a safety mechanism, but so long as no one else uses the
block device, yes it's safe. I'd be really surprised if it made a
difference though.
Something else you could try that might even faster is to add O_EXCL
to the test program and see if it helps us get to a reproducer.
- Ted
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
