public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Linux UDF support
Date: Sun, 24 Aug 2014 14:46:46 +0200	[thread overview]
Message-ID: <201408241446.47042@pali> (raw)

[-- Attachment #1: Type: Text/Plain, Size: 1211 bytes --]

Hi,

I would like to know what is state of linux UDF driver. It is 
experimental or is now suitable for storing data?

According to wikipedia [1] UDF has open specification format and 
can be used also for HDDs (not only optical discs).

In OS support table is written that all major and other minor OSs 
support UDF FS (without needs for additional programs).

So it looks like UDF is good candidate for multi OS filesystem. 
Are there any disadvantages for using UDF on e.g USB flash disk? 
(when I want read/write support on Linux, Windows 7 and Mac OS X)

Because lot of manuals say that FAT32 (or NTFS) is only one 
solution for using USB flash disk on more OS.

On wikipedia there is one note about linux: Write support is only 
up to UDF version 2.01. Is this restriction still valid?

What will happen if I try to mount FS with UDF version 2.60 in 
R/W mode on linux? It will fallback to R/O mode? Or newly written 
files will be in previous (2.01) versions?

And last question: Is there some fsck tool for UDF? Or at least 
tool which print if FS is in inconsistent state?

[1] - http://en.wikipedia.org/wiki/Universal_Disk_Format

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2014-08-24 12:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-24 12:46 Pali Rohár [this message]
2014-08-25 12:45 ` Linux UDF support Austin S Hemmelgarn
2014-08-25 13:24   ` Pali Rohár
2014-08-25 14:05     ` Austin S Hemmelgarn
2014-08-25 21:44       ` Pali Rohár
2014-08-26  9:05 ` Jan Kara

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=201408241446.47042@pali \
    --to=pali.rohar@gmail.com \
    --cc=jack@suse.cz \
    --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