[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070416152318.GG25785@atrey.karlin.mff.cuni.cz>
Date: Mon, 16 Apr 2007 17:23:18 +0200
From: Jan Kara <jack@...e.cz>
To: Tino Keitel <tino.keitel@....de>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/6] UDF cleanup and fixes
> On Thu, Apr 12, 2007 at 18:01:12 +0200, Jan Kara wrote:
> > On Wed 04-04-07 08:36:20, Tino Keitel wrote:
> > > On Mon, Apr 02, 2007 at 10:48:27 -0400, Chuck Ebbert wrote:
> > >
> > > [...]
> > >
> > > > Well, it works for me on 32-bit as well, right up to 100% full.
> > > > No problems at all...
> > >
> > > Maybe it depends on the kernel. I patched 2.6.20 with the patches
> > > above and got the described behaviour.
> > I've sent you an email with a few questions but probably it got lost in
> > the noise... Are you able to reproduce the problem? Have you reproduced the
> > problem on a freshly created UDF image or was it some older image?
>
> Hi,
>
> I can't remember of any errors in the kernel or about not available
> space. It was an image file that I expermimented with, and I did
> multiple mkudffs runs on the file. Could it be that the behaviour was
> caused by stale data inside the image?
OK, thanks for info. Umm, I don't find it likely that some stale data
in the image would cause this but maybe something could confuse mkudffs
(like it was expecting zeros somewhere where they were not). If you had
some recipe how to reproduce the problem (it would be enough if you had
something like: I have this file, I run mkudffs, mount it, see wrong
free blocks count), I can have a look at it. Otherwise, it's hard to
track it down...
Honza
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists