mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Jeff Merkey" <jmerkey@timpanogas.com>
Cc: "Jim Mostek" <mostek@sgi.com>, <andreas@andreas.org>,
	<mcai7et2@stud.umist.ac.uk>, <linux-kernel@vger.rutgers.edu>,
	Stephen Tweedie <sct@redhat.com>
Subject: Re: XFS and journalling filesystems
Date: Tue, 1 Jun 1999 00:17:03 +0100 (BST)	[thread overview]
Message-ID: <14163.6255.462769.27934@dukat.scot.redhat.com> (raw)
In-Reply-To: <012201bea93f$db9d1050$e6976dcf@TRGMERKEYNT2000>

Hi,

On Fri, 28 May 1999 13:25:33 -0600, "Jeff Merkey"
<jmerkey@timpanogas.com> said:

> getting the NetWare FS (FENRIS) ready for open source next Tuesday,
> hopefully it may be helpful to all, including you guys -- we are putting ALL
> of it under the GPL (less the NT specific IFS code which is about 18,000
> lines oddly enough)).  Sounds like the term "journalling" is like the term
> "clustering" from an industry perspective, 

No, it is a true transactional journal with ACID semantics.  It just
doesn't necessarily include data.  

> and some FS's aren't really journalled, but reapply this term for
> marketing positioning.  

That is the standard definition of the term in the fs community on
Unix.  Sounds like you are the one trying to redefine it!

> A log based file system that logs user writes and allows rollbacks
> is what most folks assume when the term "journalling" is used.  

No.  You may be thinking of a log-structured filesystem, but that is
_completely_ different from metadata journaling (which of course
doesn't mean that marketing depts don't sometimes try to confuse
them).  An LFS is necessarily journaled, but not all journaled
filesystems are log structured.

--Stephen

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

       reply	other threads:[~1999-06-01  0:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199905281653.LAA61598@fsgi344.cray.com>
     [not found] ` <012201bea93f$db9d1050$e6976dcf@TRGMERKEYNT2000>
1999-05-31 23:17   ` Stephen C. Tweedie [this message]
     [not found] <76D8782817C5D211A37400104B0C84B029C52F@nz-wlg-exch-1.nz.unisys.com>
1999-05-31  2:14 ` Ralf Baechle
     [not found] ` <3753A4A5.C2A4FE91@engr.sgi.com>
     [not found]   ` <199906010928.CAA04308@pizda.davem.net>
1999-06-01 10:15     ` Dan Koren
     [not found] <E10m0gq-0000pk-00@the-village.bc.nu>
1999-05-27 19:11 ` Dan Koren

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=14163.6255.462769.27934@dukat.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=andreas@andreas.org \
    --cc=jmerkey@timpanogas.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=mcai7et2@stud.umist.ac.uk \
    --cc=mostek@sgi.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

all inboxes | Powered by JetHome®