No. The data is not redistributed. Your original server conf file has to be the same. If you plan to add servers, after you have created data, then your config file must have been setup with enough handles to deal with the new servers. If you send me your current server conf file, I can take a look for you.
Becky On Tue, Mar 29, 2016 at 4:13 PM, David Humphreys < [email protected]> wrote: > Thank you so much. I used the svn pull and 'prepare' was the magic word. > Compiled ok and working. I'm currently copying a great deal of stuff to a > single disk, single server. > I didn't see anything in the documentation about adding to the storage > pool. I guess that the config file has to be updated and distributed to all > the servers, old and new, with the old servers being restarted. > I am wondering whether the data is then redistributed across the greater > pool. > I am interested also in the redundancy, which I read was controllable on a > file by file basis with attributes. > Plenty to explore, thank you. > David. > > Sent from my Sony Xperia™ smartphone > > > ---- Becky Ligon wrote ---- > > > Also, is you pull from the SVN repository, you must issue ./prepare before > trying to configure. > > Becky > > On Tue, Mar 29, 2016 at 9:47 AM, Mike Marshall <[email protected]> > wrote: > >> These packages (I'm looking at them from an rpm package manager >> perspective) will probably be enough to enable you to build a >> working configure: >> >> $ rpm -qa | grep m4 >> m4-1.4.17-8.fc23.x86_64 >> $ rpm -qa | grep autoconf >> autoconf-2.69-21.fc23.noarch >> $ rpm -qa | grep automake >> automake-1.15-4.fc23.noarch >> $ rpm -qa | grep libtool >> libtool-ltdl-2.4.6-8.fc23.x86_64 >> >> When I run configure on a new machine, sometimes configure fails >> for lack of some package or other... if that happens to you anywhere >> along the path of running configure for Orangefs, just try to figure out >> how to "yum install" (or whatever package manager your Linux uses) >> the missing part and run configure again... The configure script >> will give you helpful hints as to what dependency caused it to >> fail. If you didn't configure your Linux instance as a >> "development platform" (or something similar) you might find that you >> have to install several things, like flex or bison, to get configure to >> run >> all the way through... >> >> The out-of-tree kernel module needs to work with its matching >> userspace part (don't mix 2.9.3 kernel module with 2.9.4 Orangefs >> userspace), but the upstream version of the kernel module will >> probably work with 2.9.3 and beyond, certainly with 2.9.4 and >> beyond... >> >> Orangefs is real easy to compile, configure and turn on/off, especially >> after you have done it a couple of times, good luck! >> >> -Mike >> >> >> On Tue, Mar 29, 2016 at 8:27 AM, Boyd Wilson <[email protected]> wrote: >> > We are working to release 2.9.5 (2.9.4 was a release we did in >> conjunction >> > with EMC and the 2TIERS project, so was not a fully tested public >> release). >> > We are getting extremely close to 2.9.5, so you can grab a copy of >> trunk out >> > of svn and it should have what you need. >> > >> > -b >> > >> > On Tue, Mar 29, 2016 at 2:19 AM David Humphreys >> > <[email protected]> wrote: >> >> >> >> I have become aware of orangefs only as a result of its integration >> with >> >> the latest kernel release. >> >> I have been tracking ceph for a long time, but have not found it to be >> >> very user friendly: difficult to manage and difficult to make work in a >> >> robust way. >> >> Orangefs seems to provide some similar functionality, and my initial >> >> experiments yesterday seemed to confirm usability. >> >> The problem that I find is that the latest release (2.9.3) does not >> seem >> >> to contain kernel module code that will build with current kernels (my >> >> attempts failed, and references are made to 2.6.x series, and stuff has >> >> changed, I think, at 4.0). >> >> This shouldn't matter with 4.6, because orangefs is included by Linus. >> >> However when trying to mount an orangefs share the mount command >> hangs, and >> >> dmesg shows that the kernel is complaining that userspace declares >> version >> >> 20903, but 20904 is required. >> >> (those numbers from memory of yesterday, and not on the screen in >> front of >> >> me now, but I'm sure that I have not misremembered). >> >> It looks like we might need a 2.9.4 release? I tried compiling the svn >> >> version, but couldn't overcome the lack of an 'autogen.sh' to do the >> right >> >> autotools suff to make a working 'configure'. >> >> I hope someone can help me put the 4.6 kernel orangefs to the test. >> >> Thank you in anticipation. >> >> David >> >> >> >> Sent from my Sony Xperia™ smartphone >> >> >> >> _______________________________________________ >> >> 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
