From: root <libor@conet.cz>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reading from file in module fails
Date: Mon, 3 May 2004 14:07:25 +0200 [thread overview]
Message-ID: <20040503120725.GA27213@Loki> (raw)
In-Reply-To: <20040503114859.GC31513@harddisk-recovery.com>
On Mon, May 03, 2004 at 01:48:59PM +0200, Erik Mouw wrote:
> On Mon, May 03, 2004 at 01:43:16PM +0200, Libor Vanek wrote:
> > > (BTW, if you need to copy files from kernel, it's usually a sign of bad
> > > design)
> > It's not bad design - what I'm doing is writing snapshots for VFS as
> > my diploma thesis. And I need to create copy of file before it's
> > changed (copy-on-write). There is no other way how to do it in
> > kernel-space (and user-space solutions like using LUFS are really
> > slow)
> Have a look at the cowlinks (copy-on-write links) thread from last
> month, it might do the trick.
Hmmm, that seems to have several serious disadvantages:
- it's not filesystem/user-space SW independent (requires modifying them - as far as I understand how it's done)
- needs to "touch" all existing files/dirs (maybe I'm wrong but from very first look it seems to me that I need to setup "cow" flag on each file/dir I want to "cow") - my approach should be "atomic" even when I need to setup snapshot on directory containing 100s thousands of files/dirs (and that's an average server I'm thinking of!)
Nevertheless - thanks for a tip.
Libor
next prev parent reply other threads:[~2004-05-03 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 10:50 Reading from file in module fails Libor Vanek
2004-05-03 11:35 ` Erik Mouw
2004-05-03 11:43 ` Libor Vanek
2004-05-03 11:48 ` Erik Mouw
2004-05-03 12:07 ` root [this message]
2004-05-03 12:41 ` Jan-Benedict Glaw
[not found] <1RJl8-Eo-5@gated-at.bofh.it>
[not found] ` <1RJXT-19T-37@gated-at.bofh.it>
[not found] ` <1RK7v-1gJ-9@gated-at.bofh.it>
[not found] ` <1RL3A-23k-23@gated-at.bofh.it>
2004-05-03 16:55 ` Pascal Schmidt
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=20040503120725.GA27213@Loki \
--to=libor@conet.cz \
--cc=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
/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