[Lustre-discuss] Kernel panic on mounting an OST
Ludovic Francois
lfrancois at gmail.com
Thu Dec 13 07:18:05 PST 2007
On Dec 13, 3:12 pm, Ludovic Francois <lfranc... at gmail.com> wrote:
> On Dec 13, 2:59 pm, "Ludovic Francois" <lfranc... at gmail.com> wrote:
>
> > Do you think it's possible someone overwrote the "label" with a tunefs command?
>
> or the system
>
> > I already saw it with some other file system.
We recreated Target and Index with the tunefs.lustre command:
--8<---------------cut here---------------start------------->8---
[root at oss01 ~]# tunefs.lustre --writeconf --index 0 /dev/mpath/mpath0
checking for existing Lustre data: found CONFIGS/mountdata
Reading CONFIGS/mountdata
Read previous values:
Target: lustre-OST0030
Index: 48
Lustre FS: lustre
Mount type: ldiskfs
Flags: 0x2
(OST )
Persistent mount opts: errors=remount-ro,extents,mballoc
Parameters: mgsnode=10.143.0.5 at tcp mgsnode=10.143.0.6 at tcp
failover.node=10.143.0.2 at tcp sys.timeout=80 mgsnode=10.143.0.5 at tcp
mgsnode=10.143.0.6 at tcp failover.node=10.143.0.2 at tcp sys.timeout=80
Permanent disk data:
Target: lustre-OST0000
Index: 0
Lustre FS: lustre
Mount type: ldiskfs
Flags: 0x102
(OST writeconf )
Persistent mount opts: errors=remount-ro,extents,mballoc
Parameters: mgsnode=10.143.0.5 at tcp mgsnode=10.143.0.6 at tcp
failover.node=10.143.0.2 at tcp sys.timeout=80 mgsnode=10.143.0.5 at tcp
mgsnode=10.143.0.6 at tcp failover.node=10.143.0.2 at tcp sys.timeout=80
Writing CONFIGS/mountdata
[root at oss01 ~]#
--8<---------------cut here---------------end--------------->8---
But now we have some problems to remount the file system, could you
confirm us this command just rewrite the index?
Best Regards, Ludo
--
Ludovic Francois +33 (0)6 14 77 26 93
System Engineer DataDirect Networks
More information about the lustre-discuss
mailing list