Could there be someway to hardwire the stripe size in the source-code? Since Im not sure what the problem with patch is.
I tried this on my own, by modifying PINT_dist* get_default_distribution in the sys-create.sm file . I commented out the code to fetch a configuration from the server configuration file to get the distribution name and now the function only performs dist=PINT_dist_create(PVFS_DIST_SIMPLE_STRIPE_NAME); So this should then lift up the default stripe size from the pvfs2_dist_simple_stripe.h. Right? But it still does not switch to a stripe size of my choice. I work with pNFS as well and CITI's pnfs/pvfs2 [which also uses pvfs2-1.5.1] works fine when I simply edit the stripe size at the header file mentioned above. Let me also verify that when I use PVFS2 I do not use it via the VFS, hence I am not involving the kernel module here. If anyone requires, logs please let me know. Nirmal Nirmal Thacker wrote: > Ok , the patch does the job- in modifying the code correctly that is. > I see the bug in the code and I see that the patch fixes it. However, > the problem still persists. > The error is similar as well: > > [D 14:05:40.412091] PVFS2 Server version 1.5.1 starting. > [E 14:05:40.422537] Error: /home/thacker/etc/pvfs2-fs.conf line 47: > Option can't be defined in that context[E 11/05 14:05] Could not find > handle range for host (null) > [E 11/05 14:05] Please make sure that the host names in > /home/thacker/etc/pvfs2-fs.conf and > /home/thacker/etc/pvfs2-server.conf-node15 are consistent > [D 11/05 14:05] PVFS2 Server: storage space created. Exiting. > > Cannot find handle range? Seems to be fine without the Distribution > sub-section > > Does the order in which these subsections appear matter ? I've jus added > them right after the default <StorageHints> subsection > > Nirmal > > Nirmal Thacker wrote: > >> Hi Phil, >> >> Yes I have the patch in the extracted directory of PVFS2-1.5.1 and I >> apply the patch using >> >> patch -p0 < patch >> Although the patch succeeds, I still face the issue. >> >> I have been going through the code too , since the patch only modifies a >> single line. >> >> For one the patch begins at line 1248, but line 1248 in pvfs2-1.5.1 has >> something entirely different. I still dont understand though, how the >> patch succeeds >> >> For another, I think the patch refers to the function >> DOTCONF_CB(exit_distribution_context) which is at line 1039 in my >> server-config.c . I modified the configuration context there to >> CTX_FILESYSTEM as does the patch, but the problem persists. >> >> Nirmal >> >> >> >> Phil Carns wrote: >> >> >>> Are you sure that you applied the patch correctly? That fixes the >>> problem when I try the same scenario here. >>> >>> -Phil >>> >>> Nirmal Thacker wrote: >>> >>> >>>> The patch did not help either. It brings up the same error. >>>> >>>> Could there be more patch releases which I can try? >>>> >>>> >>>> Phil Carns wrote: >>>> >>>> >>>>> This was a bug in our older releases. You can try applying this patch >>>>> to fix it if you are still stuck on 1.5.1: >>>>> >>>>> http://www.pvfs.org/fisheye/rdiff/PVFS?csid=MAIN:slang:20070625220806&u&N >>>>> >>>>> >>>>> -Phil >>>>> >>>>> Nirmal Thacker wrote: >>>>> >>>>> >>>>>> Phil: >>>>>> >>>>>> I did add the Distribution context to my pvfs2-fs.conf , and restarted >>>>>> the server nodes, and received an "Option cant be defined in that >>>>>> context" error. >>>>>> The error points to the Filesystem context, maybe indicating that I >>>>>> cannot declare the distribution sub-context here (?) >>>>>> >>>>>> I have attached the error and a copy of my pvfs2-fs.conf >>>>>> >>>>>> The error comes up when I create a storage space. >>>>>> >>>>>> [I have 4 storage servers and 1 MDS. I tried by reconfiguring storage >>>>>> and restarting the servers and the error persists. It also says >>>>>> that the >>>>>> host names must be consistent [see log] . Thats strange since >>>>>> otherwise, >>>>>> the servers start fine, without the Distribution context defined] >>>>>> >>>>>> Nirmal >>>>>> >>>>>> Phil Carns wrote: >>>>>> >>>>>> >>>>>>> Hi Nirmal, >>>>>>> >>>>>>> I think that you can use the same mechanisms to set distribution >>>>>>> parameters in 1.5.1 as in our newer releases. >>>>>>> >>>>>>> There is some information here about how to set the strip size at run >>>>>>> time for a particular directory (no need to recompile): >>>>>>> >>>>>>> http://www.pvfs.org/fisheye/browse/PVFS/doc/pvfs2-tuning.tex?r=1.2#l208 >>>>>>> >>>>>>> >>>>>>> You can also set a default for the whole file system in your server >>>>>>> configuration file by adding a section that looks like this into your >>>>>>> <Filesystem> section: >>>>>>> >>>>>>> <Distribution> >>>>>>> Name simple_stripe >>>>>>> Param strip_size >>>>>>> Value 4194304 >>>>>>> </Distribution> >>>>>>> >>>>>>> -Phil >>>>>>> >>>>>>> Nirmal Thacker wrote: >>>>>>> >>>>>>> >>>>>>>> Hello >>>>>>>> >>>>>>>> I am using PVFS2-1.5.1 and as far as I know, to modify the default >>>>>>>> stripe size of PVFS2, I must modify the header >>>>>>>> include/pvfs2-dist-simple-stripe.h . >>>>>>>> >>>>>>>> Strangely , I did so and rebuilt the source, yet the pvfs2-viewdist >>>>>>>> still shows me the default striping for any new files created >>>>>>>> with the >>>>>>>> modified pvfs2 build! >>>>>>>> >>>>>>>> Nirmal >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Pvfs2-users mailing list >>>>>>>> [email protected] >>>>>>>> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users >>>>>>>> >>>>>>>> >> _______________________________________________ >> Pvfs2-users mailing list >> [email protected] >> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users >> >> > > _______________________________________________ > Pvfs2-users mailing list > [email protected] > http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users > _______________________________________________ Pvfs2-users mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
