[Pvfs2-users] db env fixes, ref count fixes etc

[Joerg Bashir]

Murali,

This patch applied cleanly to CVS, and built cleanly on 64 and 32 bit 
platforms.

I am able to successfully start the pvfs2-server and client on a 32 bit 
userspace on a 64 bit kernel with the pvfs2 kmod built on a 64 bit userspace 
machine.  Mounting pvfs and read/writing are also successfull.

My configuration is:
Kernel 2.6.16.5 (will upgrade once the Java issues are worked out.)
OS Debian/Unstable (more or less current)
PXE Boot with NFSROOT

The boxes are Dual Core AMD64x2's, 4GB RAM and 4x500GB Seagate SATA drives.

I will pose a question at some point about a more complicated configuration 
than the samples provided.  If at all possible I would like to not use RAID 
of any kind, but that makes the pvfs2-server config a lot harder.

Thank a ton for your help in getting this working for me.

-Joerg

On Friday 21 April 2006 02:27, Murali Vilayannur wrote:
> Hi Joerg,
> Could you try the appended patch and let us know if it fixes the issues
> that you observed on your setups?
> Attached patch fixes the env cleanup issues that were caused by a few
> leaked DB handles (i.e. handles returned by db_create() which were
> not closed when db->open()/db->setflags() fails).
> Also fixes the env path to point to the storage space top level directory
> for db to store some of its temp.  config files, (I think)
> On shutdown env removes all these temp. files.
> Also fixes keyval DB handles not being sync'ed/closed upon termination.
> Thanks again for the reports,
> Regards
> Murali
>
> On Thu, 20 Apr 2006, Murali Vilayannur wrote:
> > Hi Joerg,
> > Can you try the attached patch and see if it works out? Hopefully, it
> > should fix things..
> > Thanks,
> > Murali
> >
> > On Thu, 20 Apr 2006, Joerg Bashir wrote:
> > > On Thursday 20 April 2006 18:14, Joerg Bashir wrote:
> > > > On Thursday 20 April 2006 18:03, Joerg Bashir wrote:
> > > > > The relevant portions...
> > > > >
> > > > > listen(4, 256)                          = 0
> > > > > stat64("/var/tmp", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=80, ...})
> > > > > = 0 open("__db.001", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0660) = -1
> > > > > EROFS (Read-only file system)
> > > > > gettimeofday({1145581232, 794374}, NULL) = 0
> > > > > stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=56, ...}) =
> > > > > 0 write(3, "[E 01:00:32.794374] src/io/trove"..., 103) = 103
> > > >
> > > > Actually, it does one of these earlier for some reason.
> > > >
> > > > chdir("/")                              = 0
> > > >
> > > > / is read-only on this system
> > >
> > > So I got around this by telling it to chdir to /var/tmp.
> > >
> > > Also, on the 64 bit / 32 bit issue:
> > >
> > > I had to recompile the kernel module "make kmod" of pvfs2 on the 32 bit
> > > userspace / 64 bit kernel client node in order to create 32 bit
> > > pvfs2-client binaries and such.  Once that was done, they worked with
> > > the 64 bit pvfs2 kernel module I had already loaded previously.
> > >
> > > I'm concerned about the __db files.
> > >
> > > Their location isn't specified in the config file.  I put them in
> > > /var/tmp, but that's only a tmpfs. (All these nodes are NFS rooted
> > > Debian/Unstable PXE clients)
> > >
> > > Are these files stateful, shall I place them somewhere more premanent
> > > than tmpfs. :-)
> > >
> > > > _______________________________________________
> > > > Pvfs2-users mailing list
> > > > Pvfs2-users at beowulf-underground.org
> > > > http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users