From: David Woodhouse <dwmw2@infradead.org>
To: Padraig Brady <Padraig@AnteFacto.com>
Cc: William Stearns <wstearns@pobox.com>,
ML-linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [OFFTOPIC] Hardlink utility - reclaim drive space
Date: Wed, 07 Mar 2001 14:52:19 +0000 [thread overview]
Message-ID: <12975.983976739@redhat.com> (raw)
In-Reply-To: <3AA3E63E.80101@AnteFacto.com>
In-Reply-To: <3AA3E63E.80101@AnteFacto.com> <Pine.LNX.4.30.0102191626090.29121-100000@sparrow.websense.net>
Padraig@AnteFacto.com said:
> Wouldn't it be cool to have an extended attribute for files called
> "Copy on Write", so then you could hardlink all duplicate files
> together, but when a file is modified a copy is transparently created.
> The only problem I see with this is that you wouldn't have enough
> space to store a copy of a file, what would you do in this case, just
> return an error on write?
Yep. write(2) is allowed to return -ENOSPC, even when you're not extending
the file you're writing to. Think about holes and log-structured
filesystems.
--
dwmw2
prev parent reply other threads:[~2001-03-07 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-02 19:03 [OFFTOPIC] Hardlink utility - reclaim drive space William Stearns
2001-03-05 19:17 ` Padraig Brady
2001-03-05 19:19 ` Jeremy Jackson
2001-03-06 13:57 ` Padraig Brady
2001-03-05 22:08 ` David Schleef
2001-03-07 14:52 ` David Woodhouse [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=12975.983976739@redhat.com \
--to=dwmw2@infradead.org \
--cc=Padraig@AnteFacto.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wstearns@pobox.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