From: Sven Utcke <sven.utcke@gm...> - 2010-05-29 20:13:57
> What is the most common method of storing the filesystems data
> (directories, files, etc)? MySQL, flat file, etc?
I would guess that most filesystems just mirror another fs (may it be
as a union fs, or by providing access to files over ftp/scp). Archive
FSs also seem to be quite common, where data can be said to reside in
a flat file (the archive). My own filesystem keeps metadata
(basically everything returned by stat()) in MySQL, and the actual
filedata is taken from an archive (or, rather, cached files retrieved
from archives). And some FSs basically make up the information on the
Does this help?
_ ___ ___ ___
__| |/ __|| __|/ __| The dCache File System
/ _` | (__ | _| \__ \ An archive file-system for PB of data
\__,_|\___||_| |___/ http://www.desy.de/~utcke/Data/
From: Paul Alfille <paul.alfille@gm...> - 2010-06-06 16:04:48
On Sat, May 29, 2010 at 1:15 AM, Sven Utcke <sven.utcke@...> wrote:
> Hello Mike,
> > What is the most common method of storing the filesystems data
> > (directories, files, etc)? MySQL, flat file, etc?
> from archives). And some FSs basically make up the information on the
> If you are presenting hardware information (like mine, OWFS) creating the
files on the fly makes the most sense and keeps you synced with the physical
Don't forget that access is multithreaded by default, and there are many
complex cases where more than one client is altering the same "file".