Indeed Thomas,

we are currently working on Linux Debian squeeze, so could you provide me the 
source code for the Whamcloud e2fsprogs (version 1.42.3), please???

About the problem that I described in the previous mail with the kernel module 
fsfilt_ldiskfs:

$ modprobe fsfilt_ldiskfs
FATAL: Error inserting fsfilt_ldiskfs (/ 
lib/modules/2.6.32-lustre-2.2/updates/kernel/fs/lustre/fsfilt_ldiskfs.ko): 
Unknown symbol in module, or unknown parameter (see dmesg)

Running "dmesg", we note the following:

$ dmesg
...
[81314.051179] fsfilt_ldiskfs: Unknown symbol jbd2_log_start_commit

know any solution about it???

thanks in advance

_____________________________________________
Jose Angel Herrero Velasco

Dto. Electrónica y Computadores (ATC)
Facultad de Ciencias
UNIVERSIDAD DE CANTABRIA
Telf: +34 942 202248
mail: jherr...@atc.unican.es





El 15/10/2012, a las 10:28, Thomas Stibor escribió:

> Hello Jose,
> 
> the Debian Lustre packages from 
> http://pkg-lustre.alioth.debian.org/backports/lustre-2.2.0-squeeze/
> are not working correctly with the ldiskfsprogs from
> http://pkg-lustre.alioth.debian.org/backports/current-ldiskfsprogs/
> 
> The "dirdata" mkfs option is an required option otherwise you can not
> mount the mgs/mdt. I ran into the same problem a couple of weeks
> ago. To overcome this problem I downloaded the Whamcloud e2fsprogs RPM/SRC
> package and built of them DEB a package (for Wheezy). The package can be 
> found at 
> http://web-docs.gsi.de/~tstibor/lustre-builds/ldiskfsprogs/
> When you install the package, you will find a mkfs.lustre where the
> dirdata option will run out of the box. If you have any further
> problems, let me know. I can also provide you the source code for the
> Whamcloud e2fsprogs so you can build it for Squeeze rather than for Wheezy.
> 
> Cheers,
> Thomas
> 
> On Mon, Oct 15, 2012 at 08:01:11AM +0000, Herrero Velasco, Jose Angel wrote:
>> Hello Thomas,
>> 
>> For several weeks new, I'm trying to install luster 2.2 on debian squeeze 
>> server. From what I've observed, the problem seems to be the creation of the 
>> files system "mgs/mdt" and then mount.
>> The error message about the file /etc/mke2fs.conf, seems like a "warning". 
>> To avoid this, vast with adding a new line in the file, like this:
>> 
>> ldiskfs = {
>>    blocksize = 4096
>> }
>> 
>> Initially, to create the file system "MGS/MDT," we must run mkfs.lustre 
>> avoiding default option "dirdata", which is not covered by the current 
>> version 2.2:
>> 
>> $ mkfs.lustre --fsname=lustrefs --mdt --mgs --reformat --mkfsoptions="-E 
>> stripe-width = 2-i 4096-O ^ dirdata" --failnode=mdserver-1 
>> --mgsnode=mdserver-0@tcp0 /dev/sdc1
>> 
>> After creating the system successfully, the next problem comes when 
>> committing mount the new filesystem:
>> 
>> $ mount -t luster /dev/sdc1 /mgs
>> 
>> It seems that the whole problem is loading the kernel module fsfilt_ldsikfs, 
>> which is dependent of "ldiskfs":
>> 
>> $ modprobe fsfilt_ldiskfs
>> FATAL: Error inserting fsfilt_ldiskfs (/ 
>> lib/modules/2.6.32-lustre-2.2/updates/kernel/fs/lustre/fsfilt_ldiskfs.ko): 
>> Unknown symbol in module, or unknown parameter (see dmesg)
>> 
>> Running "dmesg", we note the following:
>> 
>> $ dmesg
>> ...
>> [81314.051179] fsfilt_ldiskfs: Unknown symbol jbd2_log_start_commit
>> 
>> As we can see, there are a symbol required that is not implemented in the 
>> module. This is the key to the problem. I guess solving this, we get to 
>> create completely server Lustre MGS ?
>> 
>> Any idea if someone has managed to create the appropriate patch???
>> 
>> thanks
>> 
>> 
>> _____________________________________________
>> Jose Angel Herrero Velasco
>> 
>> Dto. Electrónica y Computadores (ATC)
>> Facultad de Ciencias
>> UNIVERSIDAD DE CANTABRIA
>> Telf: +34 942 202248
>> mail: herrer...@gestion.unican.es<mailto:herrer...@gestion.unican.es>
>> 

_______________________________________________
Pkg-lustre-maintainers mailing list
Pkg-lustre-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-lustre-maintainers

Reply via email to