search for: clustred

Displaying 13 results from an estimated 13 matches for "clustred".

Did you mean: clustered
2010 Apr 30
1
gluster-volgen - syntax for mirroring/distributing across 6 nodes
NOTE: posted this to gluster-devel when I meant to post it to gluster-users 01 | 02 mirrored --| 03 | 04 mirrored --| distributed 05 | 06 mirrored --| 1) Would this command work for that? glusterfs-volgen --name repstore1 --raid 1 clustr-01:/mnt/data01 clustr-02:/mnt/data01 --raid 1 clustr-03:/mnt/data01 clustr-04:/mnt/data01 --raid 1 clustr-05:/mnt/data01 clustr-06:/mnt/data01 So the
2010 May 04
1
Posix warning : Access to ... is crossing device
I have a distributed/replicated setup with Glusterfs 3.0.2, that I'm testing on 4 servers, each with access to /mnt/gluster (which consists of all directories /mnt/data01 - data24) on each server. I'm using configs I built from volgen, but every time I access a file (via an 'ls -l') for the first time, I get all of these messages in my logs on each server: [2010-05-04 10:50:30] W
2010 May 15
1
Input/output error when running `ls` and `cd` on directories
I'm getting Input/output errors on gluster mounted directories. First, I have a few directories I created a few weeks ago, but when I run an ls on them, their status is listed as ???????: [23:52:54] [root at clustr06 /mnt/glusterfs]# ls -al ls: cannot access lost+found: Input/output error ls: cannot access bhl: Input/output error total 1920 drwxr-xr-x 7 root root 294912 2010-05-13 19:11 .
2011 Feb 04
1
3.1.2 Debian - client_rpc_notify "failed to get the port number for remote subvolume"
I have glusterfs 3.1.2 running on Debian, I'm able to start the volume and now mount it via mount -t gluster and I can see everything. I am still seeing the following error in /var/log/glusterfs/nfs.log [2011-02-04 13:09:16.404851] E [client-handshake.c:1079:client_query_portmap_cbk] bhl-volume-client-98: failed to get the port number for remote subvolume [2011-02-04 13:09:16.404909] I
2006 May 14
16
lustre clustre file system and xen 3
Hi, I am setting up a xen 3 enviroment that has a file backend and 2 application servers with live emegration between the 2 application servers. --------- --------- | app 1 | | app 2 | --------- --------- \ / \ / \ / ---------------- | file backend | ---------------- I am planing on using lustre clustre file system on the file backend. Are there
2015 Feb 02
3
Fileserver Failover with AD and Gluster
.... Is there something more intelligent than: >> >> if not \\severA\share -> try: \\serverB\share? > > Use a common domain name for both servers (what AD does internally > for authentication), or use IP-based failover via Samba's CTDB. For Member Servers, you can use a clustred Samba installation with CTDB. But you can't on Samba AD DCs, because it's not compatible with CTDB. Regards, Marc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUz6OlAAoJEFNERvHO3m51hPMH/iCuKsSyJrIqEJV9F+jBBPEe 3kqRmYPEbO/wpMF2T3B3fps7OiQOElasudHLxj6Af83/RtcxUyv7J7uX2BBh...
2010 Jul 01
6
best practice for lustre clustre startup
Hello, I have recently installed a lustre cluster which is in a test phase now but will potentially be in 24x7 production if its accepted. I would like input from the list on what the recommendations/best practices are for configuration of a lustre cluster startup. Is it advisable to have lustre on the various server pieces (mgs/mdt/oss''s) start automatically? If not why not?
2011 Sep 12
0
cannot access /mnt/glusterfs: Stale NFS file handle
I've mounted my glusterfs share as I always do: mount -t glusterfs `hostname`:/bhl-volume /mnt/glusterfs and I can see it in df: # df -h | tail -n1 clustr-01:/bhl-volume 90T 51T 39T 57% /mnt/glusterfs but I can't change into it, or access any of the files in it: # ls -al /mnt/glusterfs ls: cannot access /mnt/glusterfs: Stale NFS file handle Any idea what could be causing
2015 Feb 02
1
Fileserver Failover with AD and Gluster
...>> if not \\severA\share -> try: \\serverB\share? >>> >>> Use a common domain name for both servers (what AD does >>> internally for authentication), or use IP-based failover via >>> Samba's CTDB. >> >> For Member Servers, you can use a clustred Samba installation >> with CTDB. But you can't on Samba AD DCs, because it's not >> compatible with CTDB. > > Sorry, I'm totally new to Samba HA. > > My file servers join AD, but are not the DC itself. Does it mean > that CTDB is an option or not? > >...
2008 Jun 27
8
Boot from OCFS2
Dear List, I''m thinking about using xen productive in our datacenter, i''m still testing around with it. Now I got some questions, just for basic understanding, we got for example this environment: 2 Nodes 1 SCSI Pool server (Connected via scsi to both nodes) Now I want to build a "cluster" so i would like to make this: Node 1 -> Primary -| | --> domU
2011 Oct 19
0
glusterFS
...ther my requirments can done though glusterFS or not. Please help me to proceed further if not let me know the suitable way for that. I have a RAID server and two RHEL-6 servers. I like to have/configure Clustered node on RAID server.That means Files on RAID server should be accessble on both the clustred nodes. I have been advised to use GFS for this purpose.But I like to know is it possible through glusterFS? If so help me to Configure So. Thanks & regards, Ramesh Kumar.G -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/piperm...
2015 Feb 02
2
Fileserver Failover with AD and Gluster
I currently plan to move my storage to Gluster. One of the anticipated advantages is to have Gluster replicate data among physical nodes, i.e. if one node dies the file service can live on. AD for authentication also replicates nice on distinct physical nodes. So the remaining single point of failure is the samba file service. Is there something more intelligent than: if not \\severA\share
2010 Jul 07
0
How to evict a dead client?
Dear, everyone We have stuck with the problem that the OSS connect one dead client or one with changed IP address all the time until we reboot the dead client. From the OSS log message, we can get the information as follows: Jul 7 14:45:07 com01 kernel: Lustre: 12180:0:(socklnd_cb.cLustre: 12180:0:(socklnd_cb.c:915:ksocknal_launch_packet()) No usable routes to 12345-202.Lustre: