public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas George <nicolas.george@ens.fr>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Filesystem for mobile hard drive
Date: Mon, 13 Feb 2006 02:07:01 +0100	[thread overview]
Message-ID: <20060213010701.GA8430@clipper.ens.fr> (raw)
In-Reply-To: <43EFD6E4.60601@cfl.rr.com>

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

Le quartidi 24 pluviôse, an CCXIV, Phillip Susi a écrit :
> If by FAT you mean FAT16, then yes, you have an 8 GB limit for the 
> entire filesystem.  Fat32 on the other hand, can handle much more and so 
> should be suitable in this aspect.

According to Wikipedia, and what I knew besides, FAT32 has a limit of 2 To
for the whole filesystem. But the limit I was talking of is the file size
limit: 4 Go perfile. Which is, nowadays, a bit short: an ISO image for a
DVD-R does not fit, for example.

>				      Fragmentation is also a property not 
> of the filesystem, but of Microsoft's filesystem drivers.  I'm fairly 
> sure that the linux fat implementations do not use absurdly stupid 
> allocation algorithms that lead to lots of fragmentation.

I am not sure about that: you can not do really good algorthms on bad data
structures, and the data structures of FAT do not provide any support to do
smart allocation.

> This can be overcome with the UDF filesystem by using the uid and gid 
> mount options, allowing the files to appear to be owned by the correct 
> local user.

That is interesting. Do you know how efficient UDF is compared to others
filesystems on normal hard drives? It is optimized for CDs and DVDs, I would
not be surprised if the performances were poor on different supports.

>	       It would be nice if the other filesystems were patched to 
> allow such options as well.

I believe that such options should not be done on a per-filesystem basis.
Something in the common code of the VFS would be more logical. 

> Network filesystems are not on disk filesystems, so they have nothing to 
> do with this discussion; you can't format a disk as "nfs" or "smb".

The idea was to mount the disk with its haphazard UIDs, and then export it
and mount it as a network filesystem over the loopback. By itself, it is
absolutely useless, but networked filesystems have UIDs mapping facilities.


Regards,

-- 
  Nicolas George

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

  reply	other threads:[~2006-02-13  1:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12 15:03 Filesystem for mobile hard drive Nicolas George
2006-02-13  0:46 ` Phillip Susi
2006-02-13  1:07   ` Nicolas George [this message]
2006-02-13  2:26     ` Phillip Susi
2006-02-13  8:59       ` Jan Engelhardt
2006-02-13  9:23       ` Kalin KOZHUHAROV
2006-02-13 16:07         ` Phillip Susi
2006-02-13 10:35       ` Nicolas George
2006-02-13 15:56         ` Phillip Susi
2006-02-13 17:18           ` Nicolas George

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=20060213010701.GA8430@clipper.ens.fr \
    --to=nicolas.george@ens.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psusi@cfl.rr.com \
    /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