I notice the following behaviour on a test system while setting up init.d
scripts to allow clean shutdown and re-start of an OSS (lustre 1.8.4)
format an OST with an external journal. The external journal is located on a
raid10 array connected to one of the network interfaces (aoe).
the OST
On Sun, 2011-03-06 at 17:43 -0800, Samuel Aparicio wrote:
I am not sure why this is happening. The external raid partitions of
relevance are all presented under the same /dev/ device when they are
stopped/re-started.
I don't think I've seen the exact messages you've produced, but I have
seen
Hello!
On Mar 6, 2011, at 8:43 PM, Samuel Aparicio wrote:
now an attempt to re-mount the OST fails with
LDISKFS-fs (md14): failed to open journal device unknown-block(152,225): -6
an e2fsck fixes this external superblock
[root@OST2 ~]# e2fsck -j /dev/etherd/e9.24p1 /dev/md14
e2fsck
i just confirmed this is what is happening: the minor number changes after a
network/driver reload. I will have to look into the mechanics to see if this
can be made fixed.
... don't see a journal_dev option in mount.lustre although the path to the
device is hardcoded at mkfs time ...
is the
On Sun, Mar 06, 2011 at 07:20:32PM -0800, Samuel Aparicio wrote:
... don't see a journal_dev option in mount.lustre although the path to the
device is hardcoded at mkfs time ...
Although the -o journal_dev=0xMMmm option is not documented in the man page, it
should still work with
