linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: adfas asd <chimera_god@yahoo.com>
To: linux-raid@vger.kernel.org
Subject: Re: Is My Data DESTROYED?!
Date: Tue, 27 Oct 2009 13:31:08 -0700 (PDT)	[thread overview]
Message-ID: <472064.4204.qm@web38802.mail.mud.yahoo.com> (raw)
In-Reply-To: <1256656849.15137.126.camel@poledra.romunt.nl>

--- On Tue, 10/27/09, Rudy Zijlstra <rudy@grumpydevil.homelinux.org> wrote:
> NFS/Samba are "bloated" as you call it, because

In my opinion they are bloated because they are outmoded and ancient.  FUSE instantly rendered them obsolete.

So sine iSCSI is out my next avenue of investigation is clustering filesystems.  They should have the file-locking problem solved, and should perform better than sshfs, much less NFS or SAMBA.


--- On Tue, 10/27/09, Ryan Wagoner <rswagoner@gmail.com> wrote:
> No NFS and Samba are not ancient bloatware. What other
> protocol would
> you use for a company file server? Rsync and SSH are not
> replacements for group file sharing.

As I say, sshfs.  Be officially turned on to FUSE and sshfs.  If you continue to decline, feel free to remain in the old-timey days grandpa.  (PS, I'm 55)


--- On Tue, 10/27/09, Bill Davidsen <davidsen@tmr.com> wrote:
> What's the problem? You generate a list of file
> checksums AND SIZES and
> do some percentage of it daily, or all of it weekly, or
> whatever
> pleases you. And every time you change or add a file you
> update the
> checksum file on the master, and send it off to the backup
> machine. Of
> course you verify on the master as well as the backup, just
> in case a
> file is damaged on the master. The nice thing about this is
> that it can
> all be automated and can send you email saying that some
> number of
> files were checked and were okay, or were not okay.
> 
> If it were my problem I would invest in two Gbit cards per
> machine, two
> *good* cables, and configure for jumbo frames. That gives
> you over
> 200MB/s transfer rate using rsync, runs over ssh by default
> for
> security, does checksums by default for reliability, should
> give you a
> nice safe copy which you can verify using the checksum
> file.

Very nice Bill, but I don't know the best way to go about these things.  This is why I keep asking for specifics.  Maybe if you pretend that I'm a dumb real estate developer...




      

       reply	other threads:[~2009-10-27 20:31 UTC|newest]

Thread overview: 94+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1256656849.15137.126.camel@poledra.romunt.nl>
2009-10-27 20:31 ` adfas asd [this message]
2009-10-27 20:39   ` Is My Data DESTROYED?! Ryan Wagoner
2009-10-27 21:00     ` Christian Pernegger
2009-10-28  0:39       ` Leslie Rhorer
2009-10-28  2:57         ` Rudy Zijlstra
2009-10-27 21:08 adfas asd
2009-10-27 21:11 ` John Robinson
2009-10-27 21:22   ` adfas asd
2009-10-27 21:31     ` Christian Pernegger
2009-10-27 21:56       ` adfas asd
2009-10-28  3:14       ` Guy Watkins
  -- strict thread matches above, loose matches on Subject: below --
2009-10-26 12:56 adfas asd
2009-10-26 18:21 ` Thomas Fjellstrom
2009-10-27 14:32   ` adfas asd
2009-10-27 14:36     ` Gabor Gombas
2009-10-27 14:40       ` adfas asd
2009-10-27 18:22         ` Ryan Wagoner
2009-10-28  9:50           ` Lars Schimmer
2009-10-27 20:45     ` Bill Davidsen
2009-10-27 20:53       ` adfas asd
2009-10-27 21:00         ` Ryan Wagoner
2009-10-27 21:05           ` adfas asd
     [not found] <70ed7c3e0910221912h70b33ca0m3df9eedd9a54c459@mail.gmail.com>
2009-10-23  2:18 ` adfas asd
2009-10-23  2:43   ` Majed B.
2009-10-23  2:59     ` adfas asd
2009-10-23  3:14       ` Majed B.
2009-10-23 19:24         ` adfas asd
2009-10-23 23:07           ` NeilBrown
2009-10-23 23:25             ` adfas asd
2009-10-23 23:39               ` Majed B.
2009-10-24  4:37               ` NeilBrown
2009-10-25  0:54       ` Leslie Rhorer
2009-10-23 22:37   ` Bill Davidsen
2009-10-23 22:41     ` adfas asd
2009-10-24  9:02   ` Luca Berra
2009-10-23  2:30 ` adfas asd
2009-10-23 22:28   ` Bill Davidsen
2009-10-26 15:38     ` Darius S. Naqvi
     [not found] <70ed7c3e0910221840o795a61b9u77774725386868e2@mail.gmail.com>
2009-10-23  2:04 ` adfas asd
2009-10-23 20:32   ` Billy Crook
2009-10-23 20:46     ` Christian Pernegger
2009-10-23 20:57       ` Mattias Wadenstein
2009-10-23 21:44         ` Billy Crook
2009-10-23 22:00           ` adfas asd
2009-10-23 22:46             ` Billy Crook
2009-10-23 22:49               ` adfas asd
2009-10-23 23:54             ` berk walker
2009-10-24  0:13               ` berk walker
2009-10-25  0:22           ` Leslie Rhorer
2009-10-23 21:55         ` adfas asd
2009-10-23 22:36           ` Guy Watkins
2009-10-23 23:05           ` Bill Davidsen
2009-10-23 23:20             ` adfas asd
2009-10-23 23:20             ` NeilBrown
2009-10-23 23:25             ` Ben DJ
2009-10-24  3:39               ` Bill Davidsen
2009-10-24 12:01                 ` adfas asd
2009-10-24 14:59                   ` Christopher Chen
2009-10-25  1:52                     ` Leslie Rhorer
2009-10-25  2:03                       ` Christopher Chen
2009-10-25  2:30                         ` Leslie Rhorer
2009-10-25  5:26                           ` Thomas Fjellstrom
2009-10-25  5:41                             ` Guy Watkins
2009-10-25  6:21                               ` Eyal Lebedinsky
2009-10-25 22:55                                 ` Guy Watkins
2009-10-26  1:36                                   ` Leslie Rhorer
2009-10-26  2:40                                     ` Guy Watkins
2009-10-26  7:32                                       ` Eyal Lebedinsky
2009-10-26 18:14                                         ` Thomas Fjellstrom
2009-10-26 23:14                                           ` John Robinson
2009-10-27  2:50                                           ` Leslie Rhorer
2009-10-27  3:15                                             ` Thomas Fjellstrom
2009-10-27 14:37                                               ` adfas asd
2009-11-02 22:53                                                 ` NiftyFedora Mitch
2009-10-26 23:21                                       ` Leslie Rhorer
2009-10-25  6:15                             ` Christopher Chen
2009-10-25 13:06                             ` Leslie Rhorer
2009-10-25 12:46                     ` adfas asd
2009-10-25 13:38                       ` Gabor Gombas
2009-10-25 15:47                         ` adfas asd
2009-10-25 18:12                           ` Christopher Chen
2009-10-25 18:33                           ` Gabor Gombas
2009-10-25 14:16                       ` Leslie Rhorer
2009-10-25 16:06                         ` adfas asd
2009-10-25 16:58                           ` Thomas Fjellstrom
2009-10-26  0:55                           ` Doug Ledford
2009-10-26 12:22                             ` adfas asd
2009-10-25 16:49                       ` Thomas Fjellstrom
2009-10-25  1:28             ` Leslie Rhorer
2009-10-23 23:49         ` berk walker
2009-10-25  1:36           ` Leslie Rhorer
2009-10-25  1:50             ` Christopher Chen
2009-10-25  2:20               ` Leslie Rhorer
2009-10-23  1:36 adfas asd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=472064.4204.qm@web38802.mail.mud.yahoo.com \
    --to=chimera_god@yahoo.com \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).