Hi everybody, I had a problem which you may be interested in. I set data=writeback in /etc/fstab for each of my ext3 partitions (because it complains on "mount -o remount,data=writeback" with "ext3: journal mode can't be altered on remount" or similar) and rebooted. Problem: / was mounted read-only, I couldn't remount it (because mount appends the options from fstab, which led to the same error). Even if I put data=ordered on the mount-option-line, it wouldn't work - because the other data= entry is seen before or after, and this gives me an error and aborts. The only way to repair this was to reboot and give the kernel the options "rw init=/bin/bash" and repair that. To avoid this problem I see some alternatives: - Don't use another journaling mode except the default on /. - use initrd or pivot_root - change mount so that multiple options with the same name are folded into one - change ext3 so that journaling changes on mounted fs's are simple ignored. Any remarks, anybody??? Regards, Phil - This message is RSA-encrypted: n=33389, e=257
Hi everybody, I had a problem which you may be interested in. I set data=writeback in /etc/fstab for each of my ext3 partitions (because it complains on "mount -o remount,data=writeback" with "ext3: journal mode can't be altered on remount" or similar) and rebooted. Problem: / was mounted read-only, I couldn't remount it (because mount appends the options from fstab, which led to the same error). Even if I put data=ordered on the mount-option-line, it wouldn't work - because the other data= entry is seen before or after, and this gives me an error and aborts. The only way to repair this was to reboot and give the kernel the options "rw init=/bin/bash" and repair that. To avoid this problem I see some alternatives: - Don't use another journaling mode except the default on /. - use initrd or pivot_root - change mount so that multiple options with the same name are folded into one - change ext3 so that journaling changes on mounted fs's are simple ignored. Any remarks, anybody??? Regards, Phil - This message is RSA-encrypted: n=33389, e=257
Stephen C. Tweedie
2001-Nov-13 15:47 UTC
Re: [PROBLEM] setting data=writeback in /etc/fstab for /
Hi, On Mon, Nov 12, 2001 at 07:24:47AM +0100, Ph. Marek wrote:> To avoid this problem I see some alternatives: > > - Don't use another journaling mode except the default on /.It should work: it just needs to be done at mount time. I'll add a persistent field to the filesystem to record the default journaling mode so that this can be done once and for all without any other user-space changes.> - use initrd or pivot_rootRight.> - change ext3 so that journaling changes on mounted fs's are simple ignored.If the user asks for something illegal, it's far better to say no than to silently drop the user's request. Cheers, Stephen
Possibly Parallel Threads
- Strane remount behaviour with ext3-2.4-0.9.4
- data=writeback option on root partition - RH 8.0
- [PATCH] virtio-blk: allow toggling host cache between writeback and writethrough
- [PATCH] virtio-blk: allow toggling host cache between writeback and writethrough
- cannot mount ext3 boot partition as r/w since 2.6.30