From: Andries Brouwer <Andries.Brouwer@cwi.nl>
To: Neil Brown <neilb@suse.de>
Cc: vherva@vianova.fi, linux-kernel@vger.kernel.org,
Andries.Brouwer@cwi.nl, Jens Axboe <jens.axboe@oracle.com>
Subject: Re: Why aren't partitions limited to fit within the device?
Date: Mon, 16 Oct 2006 08:02:27 +0200 [thread overview]
Message-ID: <20061016060227.GA3090@apps.cwi.nl> (raw)
In-Reply-To: <17714.51511.845336.721450@cse.unsw.edu.au>
On Mon, Oct 16, 2006 at 09:50:15AM +1000, Neil Brown wrote:
> On Sunday October 15, vherva@vianova.fi wrote:
> > I wonder if there's ever a change the kernel partition detection code could
> > _write_ on the disk, even when there's really no partition table?
>
> No, kernel partition detection never writes.
There is something else that writes, however, that I have gotten complaints about.
(But I have not investigated.)
People doing forensics take a copy of a disk and want to preserve
that copy as-is, never changing a single bit, only looking at it.
But it is reported that also when a partition is mounted read-only,
the journaling code of ext3 will write to the journal.
Andries
next prev parent reply other threads:[~2006-10-16 6:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 23:50 Why aren't partitions limited to fit within the device? Neil Brown
2006-10-13 1:02 ` Andries Brouwer
2006-10-13 1:31 ` Neil Brown
2006-10-13 15:07 ` Alan Cox
2006-10-13 18:16 ` jdow
2006-10-16 0:08 ` Neil Brown
2006-10-16 1:22 ` Wakko Warner
2006-10-16 1:31 ` Randy Dunlap
2006-10-16 4:09 ` Kyle Moffett
2006-10-16 6:40 ` Andries Brouwer
2006-10-16 6:43 ` dean gaudet
2006-10-16 7:28 ` Xavier Bestel
2006-10-16 10:54 ` Alan Cox
2006-10-17 6:05 ` Chris Wedgwood
2006-10-15 8:29 ` Ville Herva
2006-10-15 23:50 ` Neil Brown
2006-10-16 5:27 ` Ville Herva
2006-10-16 6:02 ` Andries Brouwer [this message]
2006-10-16 6:20 ` Ville Herva
2006-10-16 6:27 ` dean gaudet
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=20061016060227.GA3090@apps.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=vherva@vianova.fi \
/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