[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#529629: marked as done ([SQUEEZE] Add a note about ext3 option "data" change from "ordered" to "writeback")

Your message dated Wed, 26 Nov 2014 08:40:04 +0100
with message-id <547583D4.20206@thykier.net>
and subject line Re: Bug#529629: Add a note about ext3 option "data" change from "ordered" to "writeback"
has caused the Debian Bug report #529629,
regarding [SQUEEZE] Add a note about ext3 option "data" change from "ordered" to "writeback"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

529629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529629
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release-notes

This is a note that I suggest to add to the next Installation manual
since it is about a possible problem that would render your system

Starting with 2.6.30 kernels, ext3 default mount option is now
data=writeback instead of "data=ordered". If you have "data=ordered"
in /etc/fstab then you will not be able to mount read/write your file
system after upgrading kernel from 2.6.29.

When the new kernel starts, it mount the root volume using default file
system option. Then, when remounting the file system as read/write, only
a few options can be changed. Option "data" cannot be changed.

If your /etc/fstab contain "data=ordered", the kernel will write this
EXT3-fs: cannot change data mode on remount
and will not remount the file system as read/write. This will, of
course, make your system unusable (or, let's say... really secure) and
you will not be able to change /etc/fstab in any way.

The solution is to use kernel parameter "rootflags=" and specify
"data=ordered" in order to permit the switch from read only to
read/write while starting up the system. Once the system has been
mounted, change /etc/fstab removing "data=ordered" or change your boot
loader in order to always pass the appropriate rootflags.

If you are already using data=journal, since this is not a default
option, you are already also specifying rootflags parameter, so nothing
should be changed.


--- End Message ---
--- Begin Message ---
On Fri, 5 Apr 2013 14:55:21 +0200 Julien Cristau <jcristau@debian.org>
> On Sun, Mar 31, 2013 at 18:22:03 -0400, David Prévot wrote:
> > Hi Giuseppe,
> > 
> > Le 31/03/2013 18:05, Giuseppe Sacco a écrit :
> > [...]
> > 
> > It might be a bit too late to fix the Squeeze release notes, OMMV.
> > 
> If a sane patch was available then I don't see why we shouldn't update
> the squeeze rn.
> Cheers,
> Julien

Closing now, as there is no patch and (regular, non-LTS) Squeeze is EOL.


--- End Message ---

Reply to: