[aklug] Re: NTFS Mounting on Windows

The problem I had there was very slow transfer time over the network. In
my use case it is a pretty big deal because I am transferring file of
200 GB and greater. Using a drive directly plugged in through USB I was
able to get 40 MB/s transfer, which is lousy, but I think it was a lot
better than what I was getting over the network with disk read + net
transfer + disk write. I think the Ethernet setup in our office is
rather poorly designed as well, which probably doesn't help anything.
(The entire office convergences onto a single cat 5 before entering into
the server room.)

On 04/01/2016 07:01 PM, Greg Madden wrote:
> Does your use allow the use of Samba to share/archive/? files?
>
> Greg M
>
> On 04/01/2016 09:51 AM, Christopher Howard wrote:
>> Ugh... the only reason I am using NTFS is because it can be shared
>> between Linux and Windows...
>>
>> On 04/01/2016 09:46 AM, Royce Williams wrote:
>>> Could be antivirus or some other "gimme silent and total access to any
>>> new drives for a while" sort of thing.
>>>
>>> Also, semi-unrelated: be very wary of sharing NTFS disks between Linux
>>> and Windows. Specifically, strict Windows NTFS forbids characters in
>>> filenames that the default Linux implementation does not. Colons are a
>>> big one. Unless you specify the "windows_names" flag in your Linux
>>> mount, it will happily let you create Windows-incompatible filenames
>>>
>>> Here's the kicker. If you then take that drive and plug it into a
>>> Windows system, if a filesystem check is triggered, it will
>>> *immediately* start *deleting* all "invalid" filenames without
>>> warning. Yeah.
>>>
>>> Guess who found this out the hard way. :/
>>>
>>> http://consortiumlibrary.org/lists/aklug/archive/2013-01/0038.html
>>>
>>> Royce
>>>
>>> On Fri, Apr 1, 2016 at 9:36 AM, Christopher Howard
>>> <christopher@alaskasi.com <mailto:christopher@alaskasi.com>> wrote:
>>>
>>> Does Windows do any kind of file system checks or block sorting
>>> automatically on NTFS volumes when you first plug them in (i.e.,
>>> through a USB connection)? I had this situation where I plugged a
>>> drive into a Windows box, then I tried to eject it, but the
>>> ejection process stalled (I could select eject but nothing would
>>> happen). After 10 minutes of no-response, I gave up and just
>>> unplugged the drive, which I thought would be safe because I had
>>> not actually done any writes as far as I knew. THEN the Windows
>>> box finally gave me an error saying not to unplug the device
>>> because ejection is in progress, and afterwards the files on the
>>> drive were corrupted — still there, but full of IO errors.
>>>
>>> Obvious lesson is don't unplug anything until Windows has given
>>> the okay (or better, never attach anything to a Windows box), but
>>> I am also trying to understand what might have happened on the
>>> technical level to corrupt the data.
>>>
>>> -- Christopher Howard, Computer Assistant
>>> Alaska Satellite Internet
>>> 3239 La Ree Way, Fairbanks, AK 99709
>>> 907-451-0088 <tel:907-451-0088> or 888-396-5623 <tel:888-396-5623>
>>> (toll free)
>>> fax: 888-260-3584 <tel:888-260-3584>
>>> mailto:christopher@alaskasi.com <mailto:christopher@alaskasi.com>
>>> http://www.alaskasatelliteinternet.com
>>> https://www.linkedin.com/in/christopher-howard-9429ab52
>>>
>>> ---------
>>> To unsubscribe, send email to <aklug-request@aklug.org
>>> <mailto:aklug-request@aklug.org>>
>>> with 'unsubscribe' in the message body.
>>>
>>>
>>
> ---------
> To unsubscribe, send email to <aklug-request@aklug.org>
> with 'unsubscribe' in the message body.
>

-- 
http://justonemoremathproblem.com
http://iuredivino.deviantart.com/gallery/
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.