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

Re: how to prevent filesystem check

noload is deprecated. :(

On 11/29/06, Sebastian Reitenbach <itlistuser rapideye de> wrote:

"Pengcheng Zou" <pengchengzou gmail com> wrote:
> use 'noload' option to mount the readonly ext3 filesystem on the slave
> host, so the journal will not be loaded.
with the noload option, following output is shown at the mount
 mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
 missing codepage or other error
 In some cases useful info is found in syslog - try
 dmesg | tail or so
 and in /var/log/messages:
 Nov 29 09:17:17 srv3 kernel: ext3: No journal on filesystem on sdb2

as this is a valid option, the same fs type, must be a bad superblock?
is ther anything I can do about it?

> BTW, this kind of setting could have some cache-coherence problem. why
> not do it correct way by using some kind of network filesystem (NFS)
> or clustering filesystem (GFS,Lustre)?

yes, I need to take a look at these file systems.


Ext3-users mailing list
Ext3-users redhat com

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