archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <>
To: Jan Kara <>
Cc: jean-luc malet <>,
Subject: Re: [PATCH 0/2] udf: A cleanup and a mount fix
Date: Wed, 22 Aug 2018 17:35:41 +0200	[thread overview]
Message-ID: <20180822153541.x3qzggxqe6gv3xbk@pali> (raw)
In-Reply-To: <>

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

On Wednesday 22 August 2018 17:24:35 Jan Kara wrote:
> Hi,
> On Wed 22-08-18 15:25:51, jean-luc malet wrote:
> > I didn't had time to test the patch yet but there is an issue in udf detection
> > of mount (using udf formated partition with mkfs.udf under linux)
> > when I do 
> > # mount /dev/sdx1 /some/mount/point 
> > it gives an error, syslog show and error saying exfat marker wasn't found (the
> > partion id is set to one of the windows compatible one, either exfat/ntfs or
> > one of the fat32 or 0x7 as described into
> > 35243/what-is-the-partition-id-filesystem-type-for-udf : Short answer: I would
> > suggest to use MBR id 0x07 for UDF partitions. so that it's detected by windows
> > and have a drive letter assigned)
> > but
> > #mount /dev/sdx1 /some/mount/point -t udf 
> > works fine
> > don't know where it is relevant to file the bug... 
> This is a different issue. Older versions of mkfs.udf did not wipe all
> locations on disk where other filesystems (previous filesystems on the
> media) could have their identifications. So mount finds exfat signature,
> tries to mount the device as FAT which fails (as UDF has already
> overwritten lots of its metadata). Right, Pali?

Yes, older versions of mkudffs (mkfs.udf) prior to 2.0 did not do any
cleanup. Just write new needed UDF structures to device. UDF itself does
not use first 32kB of disk, therefore any existing FAT/NTFS/ext*
signatures stay there. So ideally prior using older mkudffs erase first
10MB of disk, this should be enough to wipe all existing filesystem
signatures. Or use new version of mkudffs 2.0+.

Pali Rohár

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2018-08-22 19:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 13:54 [PATCH 0/2] udf: A cleanup and a mount fix Jan Kara
2018-08-21 13:54 ` [PATCH 1/2] udf: Remove dead code from udf_find_fileset() Jan Kara
2018-08-21 13:54 ` [PATCH 2/2] udf: Fix mounting of Win7 created UDF filesystems Jan Kara
     [not found] ` <>
2018-08-22 15:24   ` [PATCH 0/2] udf: A cleanup and a mount fix Jan Kara
2018-08-22 15:35     ` Pali Rohár [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180822153541.x3qzggxqe6gv3xbk@pali \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).