Re: Debian Lenny OpenSSI with LVM and RAID 1

Hi John,

Thanks for getting back to me and I also liked you post on the OpenSSI filesystem as well.

In the other post, I noticed that you mentioned " Linux filesystem stacks a CFS layer " which I assume that OpenSSI is using FUSE or FiST to stack the filesystem, but I had problem to install the "fuse-tools" which seems to be some problem with the udev as I know that we will have single-point failure with this topology, but will also have a redundant backup over the nodes as well using this approach. Additionally, I have the cluster Interconnect on a Gigabit network so that local bandwidth is not really a problem for the moment.

http://romanrm.ru/en/mhddfs

http://svn.uvw.ru/mhddfs/trunk/README

I was trying to load it into the main server but seem to get errors and as being afraid of crashing the cluster, any ideas on what I should do to install the Fuse-Tools so that I can mount stackable filesystems?

-------------------------------------------------

spartan:/mnt# apt-get install mhddfs

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  fuse-utils
The following NEW packages will be installed:
  fuse-utils mhddfs
0 upgraded, 2 newly installed, 0 to remove and 2 not upgraded.
Need to get 0B/38.2kB of archives.
After this operation, 213kB of additional disk space will be used.
Do you want to continue [Y/n]?
WARNING: The following packages cannot be authenticated!
  fuse-utils mhddfs
Authentication warning overridden.
Selecting previously deselected package fuse-utils.
(Reading database ... 102736 files and directories currently installed.) Unpacking fuse-utils (from .../fuse-utils_2.7.4-1.1+lenny1_i386.deb) ...
Selecting previously deselected package mhddfs.
Unpacking mhddfs (from .../mhddfs_0.1.12-1_i386.deb) ...
Processing triggers for man-db ...
Setting up fuse-utils (2.7.4-1.1+lenny1) ...
creating fuse group...

udev active, skipping device node creation.
invoke-rc.d: WARNING: Service udev has no entry in rc.nodeinfo
invoke-rc.d: Starting only on initnode
Usage: /etc/init.d/udev {start|stop|restart|force-reload}
invoke-rc.d: initscript udev, action "reload" failed.

dpkg: error processing fuse-utils (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of mhddfs:
 mhddfs depends on fuse-utils; however:
  Package fuse-utils is not configured yet.
dpkg: error processing mhddfs (--configure):
 dependency problems - leaving unconfigured Errors were encountered while processing:
 fuse-utils
 mhddfs
E: Sub-process /usr/bin/dpkg returned an error code (1)

spartan:/mnt#
-------------------------------------------------

I will also be working to get DRBD installed and running so that I can establish a good failover and use pairs of nodes in the CFS configuration.

Thanks and have a great day,
Lonnie Cumberland, Prof.
Physicist
 

> -----Original Message-----
> From: John Hughes [mailto:[email protected]]
> Sent: Wednesday, August 11, 2010 7:19 AM
> To: Cumberland, Lonnie
> Cc: Scott Walters; Openssi users
> Subject: Re: [SSI-users] Debian Lenny OpenSSI with LVM and RAID 1
> 
> Cumberland, Lonnie wrote:
> > Now I am looking at the disk drives that are located on each node for
> mapping into a single filespace so that all space appears to be a
> single drive to the users.
> You can't really do this.
> 
> What you could do is have each node mount its disk on a different
> directory - possibly under /cluster/nodeX/ - then you'd have a whole
> mass of space available to all nodes.
> 
> The downside would be that each node would then be a single point of
> failure.
> 
> You could reduce the chances of failure by using pairs of nodes,
> setting
> up DRBD between pairs, then making failover CFS configurations.
> 
> Better have a lot of bandwidth between the nodes.

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev