All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: joern@wohnheim.fh-wedel.de
Cc: Sytse Wielinga <s.b.wielinga@student.utwente.nl>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH for testing] cow behaviour for hard links
Date: Sat, 13 Mar 2004 14:43:30 +0100	[thread overview]
Message-ID: <20040313134330.GC3352@openzaurus.ucw.cz> (raw)
In-Reply-To: <20040312182912.GB7087@wohnheim.fh-wedel.de>

Hi!

> >  - removed inheritance, as it's not useful in any way, not expected and breaks
> > linking of files with S_COWLINK set.
> 
> Not useful?  Without inheritance, I have to manually add the flag for
> every file/directory I add.  Each time I forget, writes go to both
> files and I notice the mess weeks later.  Naa, that's where we're now
> and why I created the patch in the first place.
> 
> What we do need, though, is a new errno.  -EMLINK is close, but still
> wrong.

I do not know your current design, but...

In ideal world there would be no COW links. System would
magically detect that you are doing cp -a, and would link
at individual block level.

Well, that would be probably too fs-specific. But introducing copyfile()
syscall, which would just link the inodes if underlying fs
supported it might be good start. On first
write into one
of linked files copy
would be done...

Only disadvantage I see is that such links would not survive
tar-backup...
				Pavel

-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         


  reply	other threads:[~2004-03-13 19:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10 19:34 [PATCH for testing] cow behaviour for hard links Jörn Engel
2004-03-10 19:35 ` [Program " Jörn Engel
2004-03-10 21:34 ` [PATCH " Jamie Lokier
2004-03-10 22:17   ` Jörn Engel
2004-03-10 23:07 ` Sytse Wielinga
2004-03-10 23:46   ` Sytse Wielinga
2004-03-12 17:48 ` Sytse Wielinga
2004-03-12 18:18   ` Jörn Engel
2004-03-12 18:29   ` Jörn Engel
2004-03-13 13:43     ` Pavel Machek [this message]
2004-03-13 19:48       ` Jörn Engel
2004-03-13 21:03         ` Pavel Machek
2004-03-15  7:45           ` Jamie Lokier
2004-03-15 10:27             ` Jörn Engel
2004-03-13 22:14       ` Jörn Engel

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=20040313134330.GC3352@openzaurus.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.b.wielinga@student.utwente.nl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.