[64studio-devel] ntfs read/write problem solved

[Gustin Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

R.Wolff wrote:
|
| Gustin Johnson schrieb:
|> -----BEGIN PGP SIGNED MESSAGE-----
|> Hash: SHA1
|>
|>
|>
|> R.Wolff wrote:
|> | OK, I have my ntfs problem solved. the line(s) in fstab now read:
|> | '
|> | /dev/hdd3 /media/Whatever ntfs umask=0002,rw,user,noauto 0 0'
|> |
|> | which has left me with root still being the owner of my
|> partitions/drives.
|> | Changing ownership as root then did it. Could I replace 'user' with my
|> username
|> | instead maybe?
|>
|> No, user means that any user can mount the partition.  There is an
|> option uid, so to use your example
|>
|
| Yeah, that's what I found out and did still later last night.
|
|> /dev/hdd3 /media/Whatever ntfs umask=0002,rw,user,noauto,uid=myusername
|>
| my fstab looks like this now for these drives/partitions:
|
| '/dev/hdd3 /media/Whatever ntfs umask=0002,uid=1000,noauto 0 0'
| I will try umask=02222 later to see if I still have write access then.

You should not have write access.  The umask=0222 is telling mount to
remove the write permission regardless of what the metadata says.  So I
could take a read write partition, with all the correct file
permissions, but if I mount it with umask=0222, all the write bits are
masked with 0.
|
|> I would *not* use the rw, and umask=0002 options unless I was using
|> ntfs-3g.  The options "ro,umask=0222" are my suggestion unless you don't
|> value your data.  :)
|>
|
| I really can't get my head around these numbers. Even after reading
the mount
| (and other) man pages, it was more confusing than helping me.

The numbers make sense when you figure it out.  Try googling for unix
file permissions to get some handy info on what the numbers mean.
Google for umask mount as well.

| libntfs9 & ntfsprogs are installed on my system. ntfs-3g doesn't seem
to be in
| the repos anymore. From my understanding, ntfs-3g was/is only a graphical
| frontend to libntfs9, no?

Nope, the ntfs-3g is a completely different driver.  As I understand it,
it uses fuseUmask is handy when working on disks that were not a part of
your system, where the user accounts may not match (user space file
systems) with wine and the ntfs.dll (the actual Microsoft driver).

If it is not listed in the repositories then you may need to enable some
Debian sources or build it from scratch.  Either way, I would feel
uncomfortable interacting with important data on an ntfs partition from
within Linux, regardless of the method.  Of course the choice is always
yours.

|> ...I have moved everything into
|> an ext3 partition (actually a USB hard drive) and installed the ext2/3
|> driver for windows.  If there is a problem it is easier for me to rescue
|> data off of an ext based file system.
|>
| I have the ext2ifs driver installed under windows as well. I wonder
how this
| performs for actually recording projects under win? Is it as fast and as
| reliable than ntfs under windows? I would consider using this
driver/filesystem
| combination under windows if it turns out as well as the native solution.
| Well, I know how to recover files from an ntfs partition, question is
always,
| will it still be useable? Would this be any different with ext3 based
filesystems?

On my USB drive there is no noticeable performance hit.  I limited by
the performance and overhead of USB anyway.


|> Hth,
|
| All info is always helpful on my quest to a better *nix understanding ;)

Hope I could help.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIH1wIwRXgH3rKGfMRAumQAJ9geOnkLnUjgNKeCYFaS+duAqjt3gCeM5ve
6Dvzq8rkYahd2qFqEPAdXuE=
=09ax
-----END PGP SIGNATURE-----