** Merge proposal linked:
https://code.launchpad.net/~crass/casper/+git/casper/+merge/453083
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/41624
Title:
Replaying journals of other OS's
Over a decade later... but this might help someone. There is a way
around this mess, with some caveats. You can set the block device to
readonly using blockdev. This works as desired a lot of the time.
However, sometimes (or perhaps everytime certain filesystems need to
replay the journal), the
What we're going to end up with here in the installer is using grub-
mount rather than mount, which guarantees a true read-only mount via
GRUB's filesystem drivers plus FUSE. os-prober has already switched to
this, and we'll switch the rest of the installer over as time permits.
--
You received
** Changed in: os-prober (Debian)
Status: New = Fix Released
--
Replaying journals of other OS's filesystems, by mounting them, is unsafe
https://bugs.launchpad.net/bugs/41624
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Closing this as won't fix. Upstream will not change this behavior and
have their arguments for that. A deviation for Ubuntu is unmaintainable.
The only way to prevent write access by Linux is to set the device
access rights to read-only.
** Changed in: linux (Ubuntu)
Status: Triaged =
Ian Jackson wrote:
You can say don't do that then but
mount -o ro
is exactly what every administrator reaches for in time of trouble,
and they expect it to do no harm.
That was exactly the point I argued on the LKML but they don't seem to
see it that way. Maybe Ben Collins can try to
Phillip Susi writes ([Bug 41624] Re: Replaying journals of other OS's
filesystems, by mounting them, is unsafe):
Which kernel you are using does not really matter because the linux
kernel developers consider this to be working as intended. I have tried
arguing with the on the LKML a few
Which kernel you are using does not really matter because the linux
kernel developers consider this to be working as intended. I have tried
arguing with the on the LKML a few times with no success. They seem to
think that the read only mount flag does not mean do not write to this
disk but
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
partman-basicfilesystems no longer automounts by default, as of Hardy,
which takes care of that part of this bug:
partman-basicfilesystems (56ubuntu4) hardy; urgency=low
* Disable automounting unless partman/automount is preseeded to true. This
makes LP #106209 much less likely to occur,
See also bug 230703.
** Also affects: iso-scan (Ubuntu)
Importance: Undecided
Status: New
** Changed in: iso-scan (Ubuntu)
Importance: Undecided = High
Status: New = Triaged
** Also affects: lupin (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lupin
This definitely also affects iso-scan. lupin is affected in theory, but
in practice I think it's quite unlikely that somebody will start Wubi
and then hibernate Windows rather than simply rebooting.
--
Replaying journals of other OS's filesystems, by mounting them, is unsafe
... and of course the Wubi installation process really does require
writing to the Windows filesystem, so the only thing that could be done
in lupin would be to refuse to function at all.
--
Replaying journals of other OS's filesystems, by mounting them, is unsafe
Marking as Triaged since the report is complete.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Incomplete = Triaged
--
Replaying journals of other OS's filesystems, by mounting them, is unsafe
https://bugs.launchpad.net/bugs/41624
You received this bug notification because you are
** Changed in: partman-basicfilesystems (Ubuntu)
Assignee: Ian Jackson (ijackson) = (unassigned)
--
Replaying journals of other OS's filesystems, by mounting them, is unsafe
https://bugs.launchpad.net/bugs/41624
You received this bug notification because you are a member of Ubuntu
Bugs,
Exactly. If you do a read only mount of an inconsistent filesystem, you
/expect/ to get inconsistent results from trying to read an inconsistent
filesystem. The whole idea though, is that you make your best effort to
access the data without modifying it and possibly causing more damage.
Since
Marking the Gutsy-allocated part of this report Incomplete and assigning
to kernel-team to remove it from the list of outstanding new/undecided
bugs against Gutsy. Hopefully at some point a decision can be made over
what to do with this, but it looks like as far as the kernel is
concerned that
TJ writes ([Bug 41624] Re: Replaying journals of other OS's filesystems,
by mounting them, is unsafe):
I've noted Phillip's comments in theLKML discussion thread on this at
http://lkml.org/lkml/2007/4/8/97
Having read that thread, I'm deeply unimpressed by the head in the
sand attitude
Ian, yes it does seem a bit pedantic although to be fair there was a
devils-advocate stance :)
I can see both arguments: On the one hand read-only should mean just
that, it should have the same effect as read-only media. On the other
hand a journalled file-system does need to replay the log to
That sounds like an acceptable workaround but I still maintain that this
is a kernel bug. Read only means you no touch.
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
Replaying journals of other OS's filesystems, by mounting them, is unsafe
** Changed in: os-prober (Debian)
Status: Unknown = Unconfirmed
--
Replaying journals of other OS's filesystems, by mounting them, is unsafe
https://bugs.launchpad.net/bugs/41624
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
** Changed in: partman-basicfilesystems (Ubuntu)
Assignee: (unassigned) = Ian Jackson
--
Replaying journals of other OS's filesystems, by mounting them, is unsafe
https://bugs.launchpad.net/bugs/41624
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
I would suggest teaching parted_server (in partman-base) about a new
command to tell whether the fs on a given partition is dirty, and making
use of that in partman-basicfilesystems where it decides whether to
automount things.
As far as os-prober goes, there was discussion about this recently
Sounds like this is a kernel bug then? Mounting a filesystem r/o should
NEVER modify the disk. Should another bug be created for that and filed
upstream?
--
Replaying journals of other OS's filesystems, by mounting them, is unsafe
https://launchpad.net/bugs/41624
--
ubuntu-bugs mailing list
24 matches
Mail list logo
