Fail-over SAN setup: ZFS, NFS, and ...?

[Kip Macy]

On Fri, Jun 26, 2009 at 3:46 PM, Kai Gallasch<gallasch at free.de> wrote:
>> Freddie Cash wrote:
>>> [Not exactly sure which ML this belongs on, as it's related to both
>>> clustering and filesystems.  If there's a better spot, let me know and
>>> 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.
>   * 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