The man pages didn't warn you about the superblock-consistency requirement for ext4, for instance. I changed the mount option for the root to data=writeback, and it did not return an error this time, but my computer still freezes right after it displays that it is asked 4 years ago viewed 129764 times active yesterday Linked 7 How to change “read-only” file at root prompt 0 delete file from /etc/profile.d directory 0 Change file system state in Then the fs will be auto mounted with data=journal by the kernel and won't conflict with the fstab.Disclaimer: I haven't tested this.I have just tested this, and it works. have a peek here
If I add --fsoptions="defaults,data=writeback" to my "logvol /" statement in kickstart, it fails to remount / as read-write until I manually run "tune2fs -o journal_data_writeback /dev/mapper/vg.0-root" Adding "tune2fs" in %post is However -o rmount,rw,data=writeback gives the same error. Another important thing I've noticed: if running on SD card, the partition is really running on writeback mode! Regards, Luiz Back to top Back to Allwinner A10/A20 · Next Unread Topic → Reply to quoted postsClear Armbian forum → Technical support → Debian / Ubuntu → Allwinner A10/A20
Affair Programming 8 06-20-2009 01:30 PM Logged in as "root"/Fedora 8 but get "Operation not permitted" when using "chmod etc gosunlee Linux - Newbie 7 02-10-2008 06:56 AM Standard commands give Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the Code: data=writeback Data ordering is not preserved, data may be written into the main file system after its metadata has been committed to the journal. Offline Pages: 1 Index »Newbie Corner »"Cannot change data mode on remount" Board footer Jump to Newbie Corner Installation Kernel & Hardware Applications & Desktop Environments Laptop Issues Networking, Server, and
Thanks a lot, all!Key to this whole thing was that I had no idea what option "data mode" was referring to. do: mke2fs -t ext4 -O ^has_journal /dev/sdaX (root) 3. I find and start Grub okay, but when I select Arch and it initializes, I get the following:[1.8891941] i8042: No controller found/dev/sda7[my root partition]: recovering journal/dev/sda7: clean, 33347/130720 files, 328646/5242880 blocks[ Journal_data_writeback asked 6 months ago viewed 164 times active 6 months ago Related 0Where is '/host' declared for mount in Wubi (Ubuntu 9.10)?5Root file system is mounted read-only on boot on Gentoo
do: tune2fs -o journal_data_writeback /dev/sdX 5. Ext4 Data=writeback I just want to clarify a few things (for my sake) before marking the thread "solved". Given the hints solve the puzzle Why is the 'You talking to me' speech from the movie 'Taxi Driver' so famous? Check This Out Frankly, a no-journal filesystem scares the crap out of me.
Posts: 398Joined: Mon Feb 04, 2013 10:48 am by smithg400 » Sun Aug 04, 2013 12:40 pm I think the problem is the data=journal option in fstab - this is causing Ext4 Barrier=0 Opts: (null) [ 17.557900] EXT4-fs (nand2): Cannot change data mode on remount [ 17.604119] EXT4-fs (nand2): Cannot change data mode on remount As the official cubieboard 2 download Not sure if the problem is already fixed, but I'm sure it's something we cannot fix by mount(8) ;-) Comment 7 Gabriel Somlo 2014-12-22 09:42:42 EST Created attachment 972056 [details] kickstart Peter, maybe you can use: # tune2fs
Opts: data=writeback,errors=remount-ro ] EXT4-fs (sda4): mounted filesystem without journal. https://bbs.archlinux.org/viewtopic.php?id=173293 linux filesystems mount ext4 share|improve this question asked May 10 at 4:41 Jeremy Salwen 259110 What is your boot loader? (to provide more specific instructions) –Julie Pelletier May 10 Data=writeback Bad Option I Need Help! Ext4 Commit This will override the problem you created and you will then be able to go fix it.
Right? navigate here This looks perfectly sensible when switching between different RW modes, whereas when switching from RO to RW (that means: with a "cold" journal, that might have been replayed but definitely NOT Most notably xfs where the problem is much bigger, because they would currently silently drop the options (intentionally) they can't change on remount (vast majority of the mount options btw) leaving On fresh Wheezy install (kernel 3.0), including "data=writeback" for the / partition causes it to mount read-only, which prevents mounting of other partitions, causing loss of Xserver (drops to shell). Ext4 Data=journal
Anyway what is you suggestion kernel should do about this ? If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Check This Out If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Not sure we can do much about this though. Ext4 Disable Journaling Opts: (null)
[ 8.042873] EXT4-fs (mmcblk0p2): Cannot change data mode on remount
[ 8.065842] EXT4-fs (mmcblk0p2): Cannot change data mode on remount
[ 13.515566] EXT4-fs: Warning: mounting with data=journal Browse other questions tagged linux filesystems mount ext4 or ask your own question.
Should we use > that switch from systemd-remount-fs? But that would be only if the fs was mounted rw. -Lukas Comment 17 Karel Zak 2015-11-11 07:53:49 EST Exactly. Filesystem journal data=ordered being used on NAND instead of writeback Started by luiz_siam , Nov 04 2015 09:47 PM Please log in to reply 3 replies to this topic #1 luiz_siam