mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juri Haberland <juri@koschikode.com>
To: phillips@bonn-fries.net (Daniel Phillips)
Cc: linux-kernel@vger.kernel.org
Subject: Re: FAT32 superiority over ext2 :-)
Date: 25 Jun 2001 15:04:47 -0000	[thread overview]
Message-ID: <20010625150447.17109.qmail@babel.spoiled.org> (raw)
In-Reply-To: <0106250203070J.00430@starship>

In article <0106250203070J.00430@starship> you wrote:
> On Monday 25 June 2001 01:49, Albert D. Cahalan wrote:
>> Daniel Phillips writes:
>> > On Monday 25 June 2001 00:54, Albert D. Cahalan wrote:
>> >> By dumb luck (?), FAT32 is compatible with the phase-tree algorithm
>> >> as seen in Tux2. This means it offers full data integrity.
>> >> Yep, it whips your typical journalling filesystem. Look at what
>> >> we have in the superblock (boot sector):
>> >>
>> >>     __u32  fat32_length;  /* sectors/FAT */
>> >>     __u16  flags;         /* bit 8: fat mirroring, low 4: active fat */
>> >>     __u8   version[2];    /* major, minor filesystem version */
>> >>     __u32  root_cluster;  /* first cluster in root directory */
>> >>     __u16  info_sector;   /* filesystem info sector */
>> >>
>> >> All in one atomic write, one can...
>> >>
>> >> 1. change the active FAT
>> >> 2. change the root directory
>> >> 3. change the free space count
>> >>
>> >> That's enough to atomically move from one phase to the next.
>> >> You create new directories in the free space, and make FAT
>> >> changes to an inactive FAT copy. Then you write the superblock
>> >> to atomically transition to the next phase.

[--snip--]

> When can we expect the patch?

Don't! Blasphemy!!!

Juri ;-) 

-- 
Juri Haberland  <juri@koschikode.com> 


      reply	other threads:[~2001-06-25 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-24 22:54 Albert D. Cahalan
2001-06-24 23:22 ` Daniel Phillips
2001-06-24 23:49   ` Albert D. Cahalan
2001-06-25  0:03     ` Daniel Phillips
2001-06-25 15:04       ` Juri Haberland [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:
  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=20010625150447.17109.qmail@babel.spoiled.org \
    --to=juri@koschikode.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@bonn-fries.net \
    /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

all inboxes | Powered by JetHome®