[Lustre-discuss] ldiskfs for MDT and zfs for OSTs?
Scott Nolin
scott.nolin at ssec.wisc.edu
Tue Oct 8 08:45:38 PDT 2013
I would check to make sure your ldev.conf file is set up with the
lustre-ost0 and host name properly.
Scott
On 10/8/2013 10:40 AM, Anjana Kar wrote:
> The git checkout was on Sep. 20. Was the patch before or after?
>
> The zpool create command successfully creates a raidz2 pool, and mkfs.lustre
> does not complain, but
>
> [root at cajal kar]# zpool list
> NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT
> lustre-ost0 36.2T 2.24M 36.2T 0% 1.00x ONLINE -
>
> [root at cajal kar]# /usr/sbin/mkfs.lustre --fsname=cajalfs --ost
> --backfstype=zfs --index=0 --mgsnode=10.10.101.171 at o2ib lustre-ost0
>
> [root at cajal kar]# /sbin/service lustre start lustre-ost0
> lustre-ost0 is not a valid lustre label on this node
>
> I think we'll be splitting up the MDS and OSTs on 2 nodes as some of you
> said
> there could be other issues down the road, but thanks for all the good
> suggestions.
>
> -Anjana
>
> On 10/07/2013 07:24 PM, Ned Bass wrote:
>> I'm guessing your git checkout doesn't include this commit:
>>
>> * 010a78e Revert "LU-3682 tunefs: prevent tunefs running on a mounted device"
>>
>> It looks like the LU-3682 patch introduced a bug that could cause your issue,
>> so its reverted in the latest master.
>>
>> Ned
>>
>> On Mon, Oct 07, 2013 at 04:54:13PM -0400, Anjana Kar wrote:
>>> On 10/07/2013 04:27 PM, Ned Bass wrote:
>>>> On Mon, Oct 07, 2013 at 02:23:32PM -0400, Anjana Kar wrote:
>>>>> Here is the exact command used to create a raidz2 pool with 8+2 drives,
>>>>> followed by the error messages:
>>>>>
>>>>> mkfs.lustre --fsname=cajalfs --reformat --ost --backfstype=zfs
>>>>> --index=0 --mgsnode=10.10.101.171 at o2ib lustre-ost0/ost0 raidz2
>>>>> /dev/sda /dev/sdc /dev/sde /dev/sdg /dev/sdi /dev/sdk /dev/sdm
>>>>> /dev/sdo /dev/sdq /dev/sds
>>>>>
>>>>> mkfs.lustre FATAL: Invalid filesystem name /dev/sds
>>>> It seems that either the version of mkfs.lustre you are using has a
>>>> parsing bug, or there was some sort of syntax error in the actual
>>>> command entered. If you are certain your command line is free from
>>>> errors, please post the version of lustre you are using, or report the
>>>> bug in the Lustre issue tracker.
>>>>
>>>> Thanks,
>>>> Ned
>>> For building this server, I followed steps from the walk-thru-build*
>>> for Centos 6.4,
>>> and added --with-spl and --with-zfs when configuring lustre..
>>> *https://wiki.hpdd.intel.com/pages/viewpage.action?pageId=8126821
>>>
>>> spl and zfs modules were installed from source for the lustre 2.4 kernel
>>> 2.6.32.358.18.1.el6_lustre2.4
>>>
>>> Device sds appears to be valid, but I will try issuing the command
>>> using by-path
>>> names..
>>>
>>> -Anjana
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7435 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20131008/8176f950/attachment.bin>
More information about the lustre-discuss
mailing list