Date: Fri, 26 Jun 2009 16:34:08 -0700 From: Kip Macy <kmacy@freebsd.org> To: Kai Gallasch <gallasch@free.de> Cc: freebsd-fs@freebsd.org Subject: Re: Fail-over SAN setup: ZFS, NFS, and ...? Message-ID: <3c1674c90906261634l22910f54r31bbb8ec972d5ebf@mail.gmail.com> In-Reply-To: <4A454FD6.1080005@free.de> References: <b269bc570906241535u59475cf2hdfe225206cf34294@mail.gmail.com> <4A42B3C7.9000500@efinley.com> <4A454FD6.1080005@free.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 26, 2009 at 3:46 PM, Kai Gallasch<gallasch@free.de> wrote: >> Freddie Cash wrote: >>> [Not exactly sure which ML this belongs on, as it's related to both >>> clustering and filesystems. =A0If there's a better spot, let me know an= d >>> I'll >>> update the CC:/reply-to.] >>> >>> We're in the planning stages for building a multi-site, fail-over SAN >>> setup > > Elliot Finley wrote: >> Why not take a look at gluster? > > Quite interesting project - http://www.gluster.org/ > > But sadly: > http://www.gluster.org/docs/index.php/Whats_New_v2.0 > > [..] > Known Issues > Some known issues and pending activities stalled for upcoming releases. > =A0 * Distribute translator: uses 64bit inode numbers, as FreeBSD doesn't > support 64bit inodes. Distribute is seen to not work on FreeBSD ino_t is still a 32-bit type, but it should be safe to make the following change to _types.h: @@ -43,7 +43,7 @@ typedef __uint64_t __fsfilcnt_t; typedef __uint32_t __gid_t; typedef __int64_t __id_t; /* can hold a gid_t, pid_t, or uid_t */ -typedef __uint32_t __ino_t; /* inode number */ +typedef __uint64_t __ino_t; /* inode number */ typedef long __key_t; /* IPC key (for Sys V IPC) = */ typedef __int32_t __lwpid_t; /* Thread ID (a.k.a. LWP) *= / typedef __uint16_t __mode_t; /* permissions */ Cheers, Kip
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3c1674c90906261634l22910f54r31bbb8ec972d5ebf>