public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas George <nicolas.george@ens.fr>
To: linux-kernel@vger.kernel.org
Subject: [UDF] (bogus?) overlap of directories and files
Date: Sun, 28 May 2006 18:18:58 +0200	[thread overview]
Message-ID: <20060528161858.GA4705@clipper.ens.fr> (raw)

[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]

Hi.

<I-tell-my-life>

I have a hard drive with an UDF filesystem, and something strange happened a
few weeks ago: I had a directory foo, then I created a file bar at a
completely different place; after that, foo was no longer a directory, it
was a plain file, a hard-link to the newly created bar, except that the link
count was wrong. Obviously there is a bug somewhere.

Since then, I spent part of my free-time to dissect my filesystem, and I
found the following strange detail.

</I-tell-my-life>


Some directories have eight allocated unrecorded (extent.length >> 30 == 1,
according to ECMA 167, 4/14.14.1.1, page 4/46) sectors at the end. The
strange thing is that some of these sectors also belong to others files or
directories, as recorded sectors.

Is this situation normal?

(For the record, I am currently using a 2.6.14.1 kernel, but I did not see
anything related in the ChangeLog of later releases.)



PS: I managed to build and run fsck.udf from OpenSolaris under GNU/Linux,
but it seems to be limited to version 2 records, while Linux produces both
version 2 and version 3 records, so it did not help. I intend to release the
tools I have written to dissect my filesystem, but they still need a lot of
work.


Regards,

-- 
  Nicolas George

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 185 bytes --]

             reply	other threads:[~2006-05-28 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-28 16:18 Nicolas George [this message]
2006-05-29  1:13 ` [UDF] (bogus?) overlap of directories and files + UDF oops Salah Coronya

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=20060528161858.GA4705@clipper.ens.fr \
    --to=nicolas.george@ens.fr \
    --cc=linux-kernel@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