Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.misc > #11716 > unrolled thread

can i use external hard drive on linux?

Started bynewbie2 <xsli2@yahoo.com>
First post2014-08-12 09:11 -0700
Last post2014-08-17 23:10 +0000
Articles 7 on this page of 27 — 13 participants

Back to article view | Back to comp.os.linux.misc


Contents

  can i use external hard drive on linux? newbie2 <xsli2@yahoo.com> - 2014-08-12 09:11 -0700
    Re: can i use external hard drive on linux? Joe Makowiec <makowiec@invalid.invalid> - 2014-08-12 16:23 +0000
    Re: can i use external hard drive on linux? Robert Heller <heller@deepsoft.com> - 2014-08-12 11:45 -0500
    Re: can i use external hard drive on linux? A <a@a.com> - 2014-08-12 18:55 +0200
    Re: can i use external hard drive on linux? Andreas Kohlbach <aug14.8.ankman@spamgourmet.com> - 2014-08-12 16:20 -0400
      Re: can i use external hard drive on linux? The Natural Philosopher <tnp@invalid.invalid> - 2014-08-12 21:40 +0100
        Re: can i use external hard drive on linux? Andreas Kohlbach <aug14.8.ankman@spamgourmet.com> - 2014-08-13 19:06 -0400
    Re: can i use external hard drive on linux? The Natural Philosopher <tnp@invalid.invalid> - 2014-08-12 21:39 +0100
    Re: can i use external hard drive on linux? Rikishi42 <skunkworks@rikishi42.net> - 2014-08-12 22:50 +0200
    Re: can i use external hard drive on linux? notbob <notbob@nothome.com> - 2014-08-12 23:51 +0000
      Re: can i use external hard drive on linux? gazelle@shell.xmission.com (Kenny McCormack) - 2014-08-13 00:56 +0000
        Re: can i use external hard drive on linux? notbob <notbob@nothome.com> - 2014-08-13 22:19 +0000
      Re: can i use external hard drive on linux? Robert Riches <spamtrap42@jacob21819.net> - 2014-08-13 02:50 +0000
    Re: can i use external hard drive on linux? noydb@no.way (Bruce Sinclair) - 2014-08-12 23:13 +0000
      Re: can i use external hard drive on linux? The Natural Philosopher <tnp@invalid.invalid> - 2014-08-13 11:44 +0100
        Re: can i use external hard drive on linux? gazelle@shell.xmission.com (Kenny McCormack) - 2014-08-13 15:28 +0000
          Re: can i use external hard drive on linux? The Natural Philosopher <tnp@invalid.invalid> - 2014-08-13 16:31 +0100
            Re: can i use external hard drive on linux? gazelle@shell.xmission.com (Kenny McCormack) - 2014-08-13 15:42 +0000
              Re: can i use external hard drive on linux? The Natural Philosopher <tnp@invalid.invalid> - 2014-08-13 20:06 +0100
                Re: can i use external hard drive on linux? gazelle@shell.xmission.com (Kenny McCormack) - 2014-08-13 19:20 +0000
            Re: can i use external hard drive on linux? Rich <rich@example.invalid> - 2014-08-13 16:04 +0000
              Re: can i use external hard drive on linux? Robert Heller <heller@deepsoft.com> - 2014-08-13 11:18 -0500
                Re: can i use external hard drive on linux? Rich <rich@example.invalid> - 2014-08-13 16:28 +0000
                Re: can i use external hard drive on linux? Robert Riches <spamtrap42@jacob21819.net> - 2014-08-14 02:49 +0000
          Re: can i use external hard drive on linux? Robert Heller <heller@deepsoft.com> - 2014-08-13 10:52 -0500
            Re: can i use external hard drive on linux? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2014-08-13 20:50 +0000
            Re: can i use external hard drive on linux? noydb@no.way (Bruce Sinclair) - 2014-08-17 23:10 +0000

Page 2 of 2 — ← Prev page 1 [2]


#11735

FromRich <rich@example.invalid>
Date2014-08-13 16:04 +0000
Message-ID<lsg29j$fu2$1@dont-email.me>
In reply to#11732
The Natural Philosopher <tnp@invalid.invalid> wrote:
> On 13/08/14 16:28, Kenny McCormack wrote:
> > In article <lsffj5$7nl$2@news.albasani.net>,
> > The Natural Philosopher  <tnp@invalid.invalid> wrote:
> > ...
> >> If its to copy to and from windows no point in having it able to accept
> >> filenames that windows cannot.
> >
> > Well, OP said his immediate goal was to use the drive to move files from
> > Linux System A to Linux System B - that is, neither to nor from Windows.
> >
> > ...
> >
> > P.S.  The best advice given so far in this thread is to try to use the
> > network to move the files instead of using the hard drive.

> Certainly works for me. Even only 100Mbps is adequate for quite a lot of 
> data...

Depending upon the distribution of file sizes, his limitation may end
up being disk seek speed rather than raw network bandwidth.  Moving
lots of 4k and under files will take more time (and not saturate the
network) than moving a bunch of 4GB video files over.

Plus, given linux<->linux, he can just run rsync and let it take care
of everything.

[toc] | [prev] | [next] | [standalone]


#11736

FromRobert Heller <heller@deepsoft.com>
Date2014-08-13 11:18 -0500
Message-ID<epudnRdzrJlFEnbOnZ2dnUU7-U2dnZ2d@giganews.com>
In reply to#11735
At Wed, 13 Aug 2014 16:04:03 +0000 (UTC) Rich <rich@example.invalid> wrote:

> 
> The Natural Philosopher <tnp@invalid.invalid> wrote:
> > On 13/08/14 16:28, Kenny McCormack wrote:
> > > In article <lsffj5$7nl$2@news.albasani.net>,
> > > The Natural Philosopher  <tnp@invalid.invalid> wrote:
> > > ...
> > >> If its to copy to and from windows no point in having it able to accept
> > >> filenames that windows cannot.
> > >
> > > Well, OP said his immediate goal was to use the drive to move files from
> > > Linux System A to Linux System B - that is, neither to nor from Windows.
> > >
> > > ...
> > >
> > > P.S.  The best advice given so far in this thread is to try to use the
> > > network to move the files instead of using the hard drive.
> 
> > Certainly works for me. Even only 100Mbps is adequate for quite a lot of 
> > data...
> 
> Depending upon the distribution of file sizes, his limitation may end
> up being disk seek speed rather than raw network bandwidth.  Moving
> lots of 4k and under files will take more time (and not saturate the
> network) than moving a bunch of 4GB video files over.
> 
> Plus, given linux<->linux, he can just run rsync and let it take care
> of everything.

And/or use ssh+tar:

tar xjvf - -C sourcedir <files> | ssh destmachine tar xjvf - -C destdir

>                                                                                                

-- 
Robert Heller             -- 978-544-6933
Deepwoods Software        -- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
heller@deepsoft.com       -- Webhosting Services
                                                                                            

[toc] | [prev] | [next] | [standalone]


#11737

FromRich <rich@example.invalid>
Date2014-08-13 16:28 +0000
Message-ID<lsg3ne$q62$2@dont-email.me>
In reply to#11736
Robert Heller <heller@deepsoft.com> wrote:
> At Wed, 13 Aug 2014 16:04:03 +0000 (UTC) Rich <rich@example.invalid> wrote:
> > 
> > The Natural Philosopher <tnp@invalid.invalid> wrote:
> > > On 13/08/14 16:28, Kenny McCormack wrote:
> > > > In article <lsffj5$7nl$2@news.albasani.net>,
> > > > Well, OP said his immediate goal was to use the drive to move files from
> > > > Linux System A to Linux System B - that is, neither to nor from Windows.
> > > >
> > > > ...
> > > >
> > > > P.S.  The best advice given so far in this thread is to try to use the
> > > > network to move the files instead of using the hard drive.
> > 
> > > Certainly works for me. Even only 100Mbps is adequate for quite a lot of 
> > > data...
> > 
> > Depending upon the distribution of file sizes, his limitation may
> > end up being disk seek speed rather than raw network bandwidth. 
> > Moving lots of 4k and under files will take more time (and not
> > saturate the network) than moving a bunch of 4GB video files over.
> > 
> > Plus, given linux<->linux, he can just run rsync and let it take
> > care of everything.

> And/or use ssh+tar:

> tar xjvf - -C sourcedir <files> | ssh destmachine tar xjvf - -C destdir

Very true.  And for a one-time transfer this is often the better route. 
Paying attention to whether one should, or should not, add a / at the
end of a path to get rsync to do what one wants is not always worth it
for a one-time transfer.

Rsync, however, will win out if one ever wishes to synchronize changes
on the source over the same path to the destination a second, or
additional, number of times.

[toc] | [prev] | [next] | [standalone]


#11743

FromRobert Riches <spamtrap42@jacob21819.net>
Date2014-08-14 02:49 +0000
Message-ID<slrnluo8to.iug.spamtrap42@one.localnet>
In reply to#11736
On 2014-08-13, Robert Heller <heller@deepsoft.com> wrote:
> At Wed, 13 Aug 2014 16:04:03 +0000 (UTC) Rich <rich@example.invalid> wrote:
>
>> 
>> The Natural Philosopher <tnp@invalid.invalid> wrote:
>> > On 13/08/14 16:28, Kenny McCormack wrote:
>> > > In article <lsffj5$7nl$2@news.albasani.net>,
>> > > The Natural Philosopher  <tnp@invalid.invalid> wrote:
>> > > ...
>> > >> If its to copy to and from windows no point in having it able to accept
>> > >> filenames that windows cannot.
>> > >
>> > > Well, OP said his immediate goal was to use the drive to move files from
>> > > Linux System A to Linux System B - that is, neither to nor from Windows.
>> > >
>> > > ...
>> > >
>> > > P.S.  The best advice given so far in this thread is to try to use the
>> > > network to move the files instead of using the hard drive.
>> 
>> > Certainly works for me. Even only 100Mbps is adequate for quite a lot of 
>> > data...
>> 
>> Depending upon the distribution of file sizes, his limitation may end
>> up being disk seek speed rather than raw network bandwidth.  Moving
>> lots of 4k and under files will take more time (and not saturate the
>> network) than moving a bunch of 4GB video files over.
>> 
>> Plus, given linux<->linux, he can just run rsync and let it take care
>> of everything.
>
> And/or use ssh+tar:
>
> tar xjvf - -C sourcedir <files> | ssh destmachine tar xjvf - -C destdir

If things don't go well with that pipeline, drop the 'v' in the
option list.  Don't know for sure about current GNU tar, but I
have seen tar versions that would intermingle the file names from
'-v' and the data stream, which would cause things to go sour on
the receiving end.

HTH

-- 
Robert Riches
spamtrap42@jacob21819.net
(Yes, that is one of my email addresses.)

[toc] | [prev] | [next] | [standalone]


#11734

FromRobert Heller <heller@deepsoft.com>
Date2014-08-13 10:52 -0500
Message-ID<opmdnVS0O889FHbOnZ2dnUU7-WudnZ2d@giganews.com>
In reply to#11731
At Wed, 13 Aug 2014 15:28:59 +0000 (UTC) gazelle@shell.xmission.com (Kenny McCormack) wrote:

> 
> In article <lsffj5$7nl$2@news.albasani.net>,
> The Natural Philosopher  <tnp@invalid.invalid> wrote:
> ...
> >If its to copy to and from windows no point in having it able to accept 
> >filenames that windows cannot.
> 
> Well, OP said his immediate goal was to use the drive to move files from
> Linux System A to Linux System B - that is, neither to nor from Windows.
> 
> Of course, the real hurdle in all this is that if he reformats it to use it
> under Linux, he will:
> 
>     a) Lose whatever files are already on the drive.
>     b) Lose (temporarily) the ability to use the drive under Windows.
> 
> Note that there are, in theory at least, workarounds for b) above (e.g.,
> ext* drivers for Windows), none of them work very well.
> 
> P.S.  The best advice given so far in this thread is to try to use the
> network to move the files instead of using the hard drive.

There is also the 'trick' of using a tar archive to move the files, since the 
tar archive will preserve the Linux filenames, owners, and permissions.  The 
name and permissions of the tar file itself are not going to be important.

> 

-- 
Robert Heller             -- 978-544-6933
Deepwoods Software        -- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
heller@deepsoft.com       -- Webhosting Services
                                                                                  

[toc] | [prev] | [next] | [standalone]


#11740

FromCharlie Gibbs <cgibbs@kltpzyxm.invalid>
Date2014-08-13 20:50 +0000
Message-ID<lsgj2m02ds@news6.newsguy.com>
In reply to#11734
On 2014-08-13, Robert Heller <heller@deepsoft.com> wrote:

> There is also the 'trick' of using a tar archive to move the files,
> since the tar archive will preserve the Linux filenames, owners, and
> permissions.  The name and permissions of the tar file itself are not
> going to be important.

By the same token, I use zip files when moving between Linux and
Windows systems.  Time stamps are preserved, and line endings in
text files can be automatically converted (LF vs. CRLF).

-- 
/~\  cgibbs@kltpzyxm.invalid (Charlie Gibbs)
\ /  I'm really at ac.dekanfrus if you read it the right way.
 X   Top-posted messages will probably be ignored.  See RFC1855.
/ \  HTML will DEFINITELY be ignored.  Join the ASCII ribbon campaign!

[toc] | [prev] | [next] | [standalone]


#11755

Fromnoydb@no.way (Bruce Sinclair)
Date2014-08-17 23:10 +0000
Message-ID<lsrg9g$3em$1@dont-email.me>
In reply to#11734
In article <opmdnVS0O889FHbOnZ2dnUU7-WudnZ2d@giganews.com>, Robert Heller <heller@deepsoft.com> wrote:
>At Wed, 13 Aug 2014 15:28:59 +0000 (UTC) gazelle@shell.xmission.com (Kenny
> McCormack) wrote:
>> In article <lsffj5$7nl$2@news.albasani.net>,
>> The Natural Philosopher  <tnp@invalid.invalid> wrote:
>> ...
>> >If its to copy to and from windows no point in having it able to accept 
>> >filenames that windows cannot.
>> 
>> Well, OP said his immediate goal was to use the drive to move files from
>> Linux System A to Linux System B - that is, neither to nor from Windows.
>> 
>> Of course, the real hurdle in all this is that if he reformats it to use it
>> under Linux, he will:
>> 
>>     a) Lose whatever files are already on the drive.
>>     b) Lose (temporarily) the ability to use the drive under Windows.
>> 
>> Note that there are, in theory at least, workarounds for b) above (e.g.,
>> ext* drivers for Windows), none of them work very well.
>> 
>> P.S.  The best advice given so far in this thread is to try to use the
>> network to move the files instead of using the hard drive.
>
>There is also the 'trick' of using a tar archive to move the files, since the 
>tar archive will preserve the Linux filenames, owners, and permissions.  The 
>name and permissions of the tar file itself are not going to be important.

Thanks you (and the OP) for the reminder. Archives can indeed be our friends. 
:)



[toc] | [prev] | [standalone]


Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.os.linux.misc


csiph-web