[lkml]   [2003]   [Jul]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: File System conversion -- ideas
Stewart Smith wrote:
> Yes it is. In fact, it is more of a problem then you think.
> Think of this simple scenario:
> a script is running that downloads a kernel patch, applies it to a tree,
> then renames the directory to $1-$patchname.
> Half way through this, during the patch, the backup script comes through
> and starts to backup the filesystem.
> Now - wipe the drive clean at the end and restore it to a sane state.
> Doing live things on storage systems without transactions, snapshots or
> whatever you want to call them is tricky at best. resizing is going to
> cause headaches.

I think of some sort of overlay filesystem on top of that *thing*. In
this case ovarlay filesystem could serve as redo log in database system.
Then we need only worry with read operations, not write. Writes will be
stored in redo log, and eventually they will be included when actual
read only filesystem will be converted.

What you think about this?

"Unix IS user friendly... It's just selective about who its friends are."
-- Tollef Fog Heen

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:46    [W:0.155 / U:11.976 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site