Re: [OpenIndiana-discuss] ntfs-3g

[Мартин Бохниг via openindiana-discuss]

> No, if ntfs is on the first partition, you have to mount p1, not p0

And?! What have I written ...?!
I have exactly written that: 

https://openindiana.org/pipermail/openindiana-discuss/2016-September/019627.html
  

"Well, that's clear that you could not mount p0.
[...]
But although FDISK correctly showed that the ntfs is on partition p1, you 
despite this wanted to mount p0."

https://openindiana.org/pipermail/openindiana-discuss/2016-September/019627.html
 

p.s. It can be expected, that /mtn did not exist, because what was wanted was 
most likely /mnt   ;)
But I think everything was already said in this thread, so I personally drop 
out, unless we start to discuss concrete plans for exFAT again.


%martin



>Понедельник, 26 сентября 2016, 15:00 UTC от Jean-Pierre André 
>:
>
>Мартин Бохниг via openindiana-discuss wrote:
>>
>>  
>> https://openindiana.org/pipermail/openindiana-discuss/2016-September/019602.html
>>
>> AS wrote:
>>
>>> ntfs /dev/rdsk/c4t0d0p0 /mtn
>> Well, that's clear that you could not mount p0.
>> In Solaris x86 p0 represents the entire disk (similar to s2 on 
>> SPARC-Solaris).
>> rmformat lists devices by their all-at-once pseudo-partition p0.
>> Clearly you have to adapt that path before mounting.
>> You were on the right way:
>>
>> Fdisk shows the following:
>>
>> Partition   StatusType  Start   End   Length%
>> =   ==  =   ===   ==   ===
>> 1   ActiveIFS: NTFS 1  38903890100
>>
>> But although FDISK correctly showed that the ntfs is on partition p1, you 
>> despite this wanted to mount p0.
>
>No, if ntfs is on the first partition, you have to mount p1, not p0
>(or the real path /devices/pci* ending with :r)
>
>ntfs /dev/dsk/c4t0d0p1 /mtn
>
>/mtn being an existing (void) directory.
>
>Jean-Pierre
>
>
>
>
>___
>openindiana-discuss mailing list
>openindiana-discuss@openindiana.org
>https://openindiana.org/mailman/listinfo/openindiana-discuss

Well, that's clear that you could not mount p0.


p.s. It can be expected, that /mtn did not exist, because what was wanted was 
most likely /mnt   ;)
But I think everything was already said in this thread, so I personally drop 
out.


%martin



>Понедельник, 26 сентября 2016, 15:00 UTC от Jean-Pierre André 
>:
>
>Мартин Бохниг via openindiana-discuss wrote:
>>
>>  
>> https://openindiana.org/pipermail/openindiana-discuss/2016-September/019602.html
>>
>> AS wrote:
>>
>>> ntfs /dev/rdsk/c4t0d0p0 /mtn
>> Well, that's clear that you could not mount p0.
>> In Solaris x86 p0 represents the entire disk (similar to s2 on 
>> SPARC-Solaris).
>> rmformat lists devices by their all-at-once pseudo-partition p0.
>> Clearly you have to adapt that path before mounting.
>> You were on the right way:
>>
>> Fdisk shows the following:
>>
>> Partition   StatusType  Start   End   Length%
>> =   ==  =   ===   ==   ===
>> 1   ActiveIFS: NTFS 1  38903890100
>>
>> But although FDISK correctly showed that the ntfs is on partition p1, you 
>> despite this wanted to mount p0.
>
>No, if ntfs is on the first partition, you have to mount p1, not p0
>(or the real path /devices/pci* ending with :r)
>
>ntfs /dev/dsk/c4t0d0p1 /mtn
>
>/mtn being an existing (void) directory.
>
>Jean-Pierre
>
>
>
>
>___
>openindiana-discuss mailing list
>openindiana-discuss@openindiana.org
>https://openindiana.org/mailman/listinfo/openindiana-discuss

Well, that's clear that you could not mount p0.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Jean-Pierre André]

Hi again,

Apostolos Syropoulos via openindiana-discuss wrote:


I feel this way of identifying a partition as rather dangerous.





After your suggestions, I have used the following command:

# ntfs-3g /dev/dsk/c4t0d0p1 /mnt

The command worked! Thank you.


Great !

Jean-Pierre




___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Jean-Pierre André]

Мартин Бохниг via openindiana-discuss wrote:


https://openindiana.org/pipermail/openindiana-discuss/2016-September/019602.html

AS wrote:


ntfs /dev/rdsk/c4t0d0p0 /mtn

Well, that's clear that you could not mount p0.
In Solaris x86 p0 represents the entire disk (similar to s2 on SPARC-Solaris).
rmformat lists devices by their all-at-once pseudo-partition p0.
Clearly you have to adapt that path before mounting.
You were on the right way:

Fdisk shows the following:

Partition   StatusType  Start   End   Length%
=   ==  =   ===   ==   ===
1   ActiveIFS: NTFS 1  38903890100

But although FDISK correctly showed that the ntfs is on partition p1, you 
despite this wanted to mount p0.


No, if ntfs is on the first partition, you have to mount p1, not p0
(or the real path /devices/pci* ending with :r)

ntfs /dev/dsk/c4t0d0p1 /mtn

/mtn being an existing (void) directory.

Jean-Pierre




___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Jean-Pierre André]

Hi Apostolos,

Apostolos Syropoulos via openindiana-discuss wrote:

Are you sure this is ntfs formatted ? Please post the output
of :



More than sure. I formated it on Windows 7 and today I tested on another
machine running Windows.




head -c 11 [device-path] | tail -c 8



# head -c 11 [device-path] | tail -c 8
[device-path]: No such file or directory
tail: 8: No such file or directory


You obviously have to replace [device-path] by the
actual device path to the partition, something like
/dev/dsk/c3t0d0p1 (for the first partition)




BTW we are talking about a plain USB flash disk.


It has to be formatted as ntfs.

Jean-Pierre


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Мартин Бохниг via openindiana-discuss]

https://openindiana.org/pipermail/openindiana-discuss/2016-September/019602.html
 

AS wrote:

> ntfs /dev/rdsk/c4t0d0p0 /mtn
Well, that's clear that you could not mount p0.
In Solaris x86 p0 represents the entire disk (similar to s2 on SPARC-Solaris).
rmformat lists devices by their all-at-once pseudo-partition p0.
Clearly you have to adapt that path before mounting.
You were on the right way:

Fdisk shows the following:

Partition   StatusType  Start   End   Length%
=   ==  =   ===   ==   ===
1   ActiveIFS: NTFS 1  38903890100

But although FDISK correctly showed that the ntfs is on partition p1, you 
despite this wanted to mount p0.
BTW the next error you might have received with this command (if specifying a 
valid partition) would probably be 
mount: /mtn: No such file or directory

Independently of that all the exFAT stuff I wrote generally applies to Hipster 
versus modern SDHX cards formatted in modern DSLR cameras, like this Sandisk 
Extreme Pro 128GB when formatted in a FullFrame Nikon:  
https://www.bueromarkt-ag.de/sd-karte_sandisk_128_gb_extreme_pro,p-sd-128sdep,l-google-prd,pd-b2c.html
  





>Понедельник, 26 сентября 2016, 13:25 UTC от Apostolos Syropoulos via 
>openindiana-discuss :
>
>>
>> I feel this way of identifying a partition as rather dangerous.
>>
>
>
>
>After your suggestions, I have used the following command:
>
># ntfs-3g /dev/dsk/c4t0d0p1 /mnt
>
>The command worked! Thank you.
>
>
>A.S.
>--
>Apostolos Syropoulos
>Xanthi, Greece
>
>___
>openindiana-discuss mailing list
>openindiana-discuss@openindiana.org
>https://openindiana.org/mailman/listinfo/openindiana-discuss

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Apostolos Syropoulos via openindiana-discuss]

>
> I feel this way of identifying a partition as rather dangerous.
>



After your suggestions, I have used the following command:

# ntfs-3g /dev/dsk/c4t0d0p1 /mnt

The command worked! Thank you.


A.S.
--
Apostolos Syropoulos
Xanthi, Greece

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Jean-Pierre André]

Jean-Pierre André wrote:

Michael Kruger wrote:

On 09/25/2016 04:24 PM, Adam Števko wrote:

HI,

out of curiosity, how was the NTFS created? When I tested this last, I
was able to mount ntfs properly. However, the partition was created by
ntfs-3g tools.

Adam



I don't recall as it's been a while since I tried. It was either created
under Windows 10, or using gparted under Linux. I never considered
trying to do it on OI. Seems to me the value of ntfs-3g would be
diminished if it can only work with partitions and filesystems created
by the tool itself.


Of course, ntfs-3g can read and write to partitions formatted
by Windows. Note however


Sorry, I was interrupted while writing this...

I wanted to mention that for reading DLLs from a Windows 10
system partition, you may need a specific plugin for decompressing
the DLL. You also need a plugin for reading deduplicated files
created by Windows Server 2012. Both plugins are available
for OpenIndiana (only for reading) on :

http://jp-andre.pagesperso-orange.fr/openindiana-ntfs-3g.html

Jean-Pierre




___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Мартин Бохниг via openindiana-discuss]

Self-correction regarding rmvolmgr:
> Do you see the point?
> It is not about mobile user events in the first place, but the point is {is 
> it connected via USB} or not.

Obviously add to this special decision-making for optical media, ZIP drives and 
Floppy disks, independently of USB or not.
Which all are quite unlikely to contain either ntfs or exFAT, but just for the 
sake of completeness.

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Мартин Бохниг via openindiana-discuss]

>Fixed devices are controlled by /etc/vfstab, you may want
>to not mount them, or mount them either read-write or read-only.

So called "removable" devices _can_ also be mounted via vfstab.
And system-filesystem-rmvolmgr _can_ be disabled via svcadm.

And it would be trivial to enhance rmvolmgr to also mount non-"removable" 
devices, if one wanted to for an experiment.

Alltogether it is an artificial distrinction, based on the expectation that all 
usb connected devices are "mobile" and that SAS or SATA (or IDE or SCSI) 
connected devices aren't.
You turn a "removable" device into "fixed storage" in 20 seconds by simply 
plugging any SATA disk behind some USB bridge.

Also I myself own a Quad-bay USB tower since 2008 and believe me - it is not a 
mobile device.

But back to your examples: 

> Why would you plug dynamically on a running system an ntfs
> device which you would not want to mount ?

No, it has nothing to do with that.
E.g. if there is no such connection event triggered, your mobile devices also 
get mounted by rmvolmgr during boot.
And in contrast: If I hot-swap add a SAS disk, even though a mobile even did in 
theory take place, nothing will get automounted, only devfsadm handles the 
device nodes and symlinks.


Do you see the point?
It is not about mobile user events in the first place, but the point is {is it 
connected via USB} or not.
The dynamic event handling stuff comes only afterwards and even if there is no 
such event, USB devices still get handled by rmvolmgr unless it was disabled 
via SMF or unless the device in question was already mounted explicitly via 
vfstab before rmvolmgr gets reached during a boot in the SMF hierarchy (and/or 
if it contains another filesystem).







>
>
>> (Although: I think the rmvolmgr is smart enough to distinguish "mobile" 
>> devices from fixed storage).
>> It would be similary to force-import / automount all zfs pools on a system 
>> (as on some other ZFS platforms).
>>
>> Are you 100% sure we want that?
>
>I mean automounting triggered by plugging in a USB device.
>You plug in the device, it mounts without having to determine
>its device patch, which depends on the USB socket you have used.
>
>Why would you plug dynamically on a running system an ntfs
>device which you would not want to mount ?
>
>> No, perhaps not.
>>
>> However, with exFAT this problem doesn't exist, as exFAT will only reside on 
>> some removable media.
>> Hence _after_ we do have fuse-exFAT support functioning well on Hipster, 
>> let's think again about your proposal, but for exFAT rather than for ntfs 
>> (or lets say: for *both*, but milited to USB storage aka "mobile devices").
>>
>>
>> regards,
>> %martin, East-Berlin
>>
>>
>>
>>> Понедельник, 26 сентября 2016, 6:56 UTC от Jean-Pierre André < 
>>> jean-pierre.an...@wanadoo.fr >:
>>>
>>> Мартин Бохниг via openindiana-discuss wrote:


  https://github.com/illumos/illumos-gate/tree/master/usr/src/cmd/rmvolmgr

>>>
>>> Thanks
>>>
>>> Jean-Pierre
>>>
>> ___
>> openindiana-discuss mailing list
>>  openindiana-discuss@openindiana.org
>>  https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>
>
>
>
>___
>openindiana-discuss mailing list
>openindiana-discuss@openindiana.org
>https://openindiana.org/mailman/listinfo/openindiana-discuss

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Мартин Бохниг via openindiana-discuss]

You are welcome, I'm glad I could help.
BTW In theory I agree myself with your proposal to have ntfs devices 
automounted.
But this would also automount huge ntfs hdd's on dual-boot systems.
(Although: I think the rmvolmgr is smart enough to distinguish "mobile" devices 
from fixed storage).
It would be similary to force-import / automount all zfs pools on a system (as 
on some other ZFS platforms).

Are you 100% sure we want that?
No, perhaps not.

However, with exFAT this problem doesn't exist, as exFAT will only reside on 
some removable media.
Hence _after_ we do have fuse-exFAT support functioning well on Hipster, let's 
think again about your proposal, but for exFAT rather than for ntfs (or lets 
say: for *both*, but milited to USB storage aka "mobile devices").


regards,
%martin, East-Berlin



>Понедельник, 26 сентября 2016, 6:56 UTC от Jean-Pierre André 
>:
>
>Мартин Бохниг via openindiana-discuss wrote:
>>
>>
>>  https://github.com/illumos/illumos-gate/tree/master/usr/src/cmd/rmvolmgr
>>
>
>Thanks
>
>Jean-Pierre
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Мартин Бохниг via openindiana-discuss]

Hi Jean-Pierre,


yes, that's what I meant:

A) He came across an exFAT _probably photo/video SDXC) card or "device".

B) The same fuse software where ntfs-3g was taken and ported from also supports 
exFAT.
And it was already ported by some Russian youngster to Solaris-sparc years ago, 
all we need to do is to rewrite (primarily the missing Makefiles) to make it 
function on x86/x64 Solaris.

Here the link I posted, this time its exFAT subfolder (I forked it 3 weeks ago 
and got it mostly built on x64) :

https://github.com/OpenSXCE-org/solaris-sparc-fuse/tree/master/fuse-exfat  


The other link I posted:

https://twitter.com/opensxce/status/771914482733969408  

brings us to a lengthy description in Russian how he thinks we should build his 
gate.
Here the link I referred there (takes a while to load) :  
http://www.tune-it.ru/web/myaut/home/-/blogs/%D0%B4%D0%BE%D0%B1%D0%B0%D0%B2%D0%BB%D1%8F%D0%B5%D0%BC-%D0%BF%D0%BE%D0%B4%D0%B4%D0%B5%D1%80%D0%B6%D0%BA%D1%83-ntfs-exfat-%D0%B2-solaris-11
  



Googling shows that other OS's have it working for ages already:


fuse exfat
https://www.google.de/search?q=fuse+exfat=utf-8=utf-8_rd=cr=SsjoV7_dL4bA6ATjlonoDA
  


I originally wanted to post this as official Illumos RFE just before they 
decided to illegally ban me again (after 2 weeks of letting me post something, 
after 3 earlier years of complete blockade).

So yes, I worked on it already and as I believe Hipster needs it still (let's 
forget the rest) - sure, after VBox5 and the agpgart fix (for i915 on <= gen5), 
I can resume this to get the remainder completed.
I'm glad if somebody joins in as I'm already on a 10fold load with the other 
projects (as scratched on in  
https://openindiana.org/pipermail/openindiana-discuss/2016-September/019609.html
 ).



Regards,
%martin





>Понедельник, 26 сентября 2016, 6:53 UTC от Jean-Pierre André 
>:
>
>Hi Martin
>
>Мартин Бохниг via openindiana-discuss wrote:
>> --->>
>> [OpenIndiana-discuss] exFAT fuse support needed __/__ Re[2]: ntfs-3g
>>  
>> https://openindiana.org/pipermail/openindiana-discuss/2016-September/019610.html
>> <<---
>
>What do you mean ? I agree that if Apostolos is using an
>exFAT formatted device, he need some exFAT support, not ntfs-3g.
> From what would you think this is the case ?
>
>And if you have an exFAT fuse driver on your workbench, this
>is great news.
>
>Jean-Pierre
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Jean-Pierre André]

Мартин Бохниг via openindiana-discuss wrote:



https://github.com/illumos/illumos-gate/tree/master/usr/src/cmd/rmvolmgr



Thanks

Jean-Pierre






Понедельник, 26 сентября 2016, 6:45 UTC от Jean-Pierre André 
:

Apostolos Syropoulos via openindiana-discuss wrote:



   Hello,

I kust wanted to check ntfs-3g and I downloaded and installed the packages from

  http://jp-andre.pagesperso-orange.fr/openindiana-ntfs-3g.html

However, it seems that it is not working.


# rmformat -l
Looking for devices...
1. Logical Node: /dev/rdsk/c2t3d0p0
Physical Node: /pci@0,0/pci1849,4391@11/cdrom@3,0
Connected Device: HL-DT-ST DVDRAM GH24NSD1  LG00
Device Type: DVD Reader/Writer
Bus: 
Size: 


I feel this way of identifying a partition as rather dangerous.

For a USB device, I first plug in a FAT-formatted USB key
which mounts automatically. Then I get its device path
which looks like /dev/dsk/c2t0d0p0:1 which gives the
device path for the first partition as /dev/dsk/c2t0d0p1.

Does anybody know where is the automount code for FAT
devices ? I would like to automount NTFS ones also.

Jean-Pierre






___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Jean-Pierre André]

Hi Martin

Мартин Бохниг via openindiana-discuss wrote:

--->>
[OpenIndiana-discuss] exFAT fuse support needed __/__ Re[2]: ntfs-3g
https://openindiana.org/pipermail/openindiana-discuss/2016-September/019610.html
<<---


What do you mean ? I agree that if Apostolos is using an
exFAT formatted device, he need some exFAT support, not ntfs-3g.
From what would you think this is the case ?

And if you have an exFAT fuse driver on your workbench, this
is great news.

Jean-Pierre




Понедельник, 26 сентября 2016, 6:34 UTC от Jean-Pierre André 
:

Both are ntfs-3g-2016.2.22AR.1, compiled by different
compilers.

Can you give details ? What is the output of

head -c 11 [device path] | tail -c 8

Jean-Pierre


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss






___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Мартин Бохниг via openindiana-discuss]

https://github.com/illumos/illumos-gate/tree/master/usr/src/cmd/rmvolmgr  




>Понедельник, 26 сентября 2016, 6:45 UTC от Jean-Pierre André 
>:
>
>Apostolos Syropoulos via openindiana-discuss wrote:
>>
>>
>>   Hello,
>>
>> I kust wanted to check ntfs-3g and I downloaded and installed the packages 
>> from
>>
>>  http://jp-andre.pagesperso-orange.fr/openindiana-ntfs-3g.html
>>
>> However, it seems that it is not working.
>>
>>
>> # rmformat -l
>> Looking for devices...
>> 1. Logical Node: /dev/rdsk/c2t3d0p0
>> Physical Node: /pci@0,0/pci1849,4391@11/cdrom@3,0
>> Connected Device: HL-DT-ST DVDRAM GH24NSD1  LG00
>> Device Type: DVD Reader/Writer
>> Bus: 
>> Size: 
>
>I feel this way of identifying a partition as rather dangerous.
>
>For a USB device, I first plug in a FAT-formatted USB key
>which mounts automatically. Then I get its device path
>which looks like /dev/dsk/c2t0d0p0:1 which gives the
>device path for the first partition as /dev/dsk/c2t0d0p1.
>
>Does anybody know where is the automount code for FAT
>devices ? I would like to automount NTFS ones also.
>
>Jean-Pierre
>
>
>
>___
>openindiana-discuss mailing list
>openindiana-discuss@openindiana.org
>https://openindiana.org/mailman/listinfo/openindiana-discuss

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Jean-Pierre André]

Apostolos Syropoulos via openindiana-discuss wrote:



  Hello,

I kust wanted to check ntfs-3g and I downloaded and installed the packages from

http://jp-andre.pagesperso-orange.fr/openindiana-ntfs-3g.html

However, it seems that it is not working.


# rmformat -l
Looking for devices...
1. Logical Node: /dev/rdsk/c2t3d0p0
Physical Node: /pci@0,0/pci1849,4391@11/cdrom@3,0
Connected Device: HL-DT-ST DVDRAM GH24NSD1  LG00
Device Type: DVD Reader/Writer
Bus: 
Size: 


I feel this way of identifying a partition as rather dangerous.

For a USB device, I first plug in a FAT-formatted USB key
which mounts automatically. Then I get its device path
which looks like /dev/dsk/c2t0d0p0:1 which gives the
device path for the first partition as /dev/dsk/c2t0d0p1.

Does anybody know where is the automount code for FAT
devices ? I would like to automount NTFS ones also.

Jean-Pierre



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Мартин Бохниг via openindiana-discuss]

--->>  
[OpenIndiana-discuss] exFAT fuse support needed __/__ Re[2]: ntfs-3g
https://openindiana.org/pipermail/openindiana-discuss/2016-September/019610.html
  
<<---

>Понедельник, 26 сентября 2016, 6:34 UTC от Jean-Pierre André 
>:
>
>Both are ntfs-3g-2016.2.22AR.1, compiled by different
>compilers.
>
>Can you give details ? What is the output of
>
>head -c 11 [device path] | tail -c 8
>
>Jean-Pierre
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Jean-Pierre André]

Michael Kruger wrote:

On 09/25/2016 02:09 PM, Apostolos Syropoulos via openindiana-discuss wrote:


  Hello,

I kust wanted to check ntfs-3g and I downloaded and installed the
packages from

http://jp-andre.pagesperso-orange.fr/openindiana-ntfs-3g.html



There is also a package in the hipster repo:

system/file-system/ntfsprogs@2016.2.22,5.11-2016.0.0.2:20160730T020527Z



However, I didn't have much luck getting that one to work either.


Both are ntfs-3g-2016.2.22AR.1, compiled by different
compilers.

Can you give details ? What is the output of

head -c 11 [device path] | tail -c 8

Jean-Pierre



Michael




___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Jean-Pierre André]

Apostolos Syropoulos via openindiana-discuss wrote:




Does this work:

ntfs-3g /dev/dsk/c4t0d0p1 /mnt




# ntfs-3g /dev/rdsk/c4t0d0p1 /mnt
ntfs_attr_pread_i: ntfs_pread failed: Invalid argument
Failed to read NTFS $Bitmap: Invalid argument
The device '/devices/pci@0,0/pci1849,4396@13,2/storage@2/disk@0,0:r,raw' 
doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?


Why does your device path ends with ",raw" ? You have
to use /dev/dsk/c.t.d.p. not /dev/rdsk/c.t.d.p.

Are you sure this is ntfs formatted ? Please post the output
of :

head -c 11 [device-path] | tail -c 8

Jean-Pierre




  A.S.
--
Apostolos Syropoulos
Xanthi, Greece





___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Jean-Pierre André]

Michael Kruger wrote:

On 09/25/2016 04:24 PM, Adam Števko wrote:

HI,

out of curiosity, how was the NTFS created? When I tested this last, I
was able to mount ntfs properly. However, the partition was created by
ntfs-3g tools.

Adam



I don't recall as it's been a while since I tried. It was either created
under Windows 10, or using gparted under Linux. I never considered
trying to do it on OI. Seems to me the value of ntfs-3g would be
diminished if it can only work with partitions and filesystems created
by the tool itself.


Of course, ntfs-3g can read and write to partitions formatted
by Windows. Note however



For that matter, I'm curious whether a Windows system would respect a
partition and NTFS filesystem created by ntfs-3g. I sure would hope so
as this utility is, after all, to help provide interoperability.


Of course it does, the main purpose is indeed to provide
interoperability. All my user files (documentation, music,
source code including ntfs-3g, etc.) are on ntfs and
shared between Windows, Linux and OpenIndiana.




___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Michael Kruger]

On 09/25/2016 04:24 PM, Adam Števko wrote:

HI,

out of curiosity, how was the NTFS created? When I tested this last, I was able 
to mount ntfs properly. However, the partition was created by ntfs-3g tools.

Adam


I don't recall as it's been a while since I tried. It was either created 
under Windows 10, or using gparted under Linux. I never considered 
trying to do it on OI. Seems to me the value of ntfs-3g would be 
diminished if it can only work with partitions and filesystems created 
by the tool itself.


For that matter, I'm curious whether a Windows system would respect a 
partition and NTFS filesystem created by ntfs-3g. I sure would hope so 
as this utility is, after all, to help provide interoperability.


Michael

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Adam Števko]

HI,

out of curiosity, how was the NTFS created? When I tested this last, I was able 
to mount ntfs properly. However, the partition was created by ntfs-3g tools.

Adam

> On Sep 25, 2016, at 10:14 PM, Michael Kruger  wrote:
> 
> On 09/25/2016 02:09 PM, Apostolos Syropoulos via openindiana-discuss wrote:
>> 
>>  Hello,
>> 
>> I kust wanted to check ntfs-3g and I downloaded and installed the packages 
>> from
>> 
>> http://jp-andre.pagesperso-orange.fr/openindiana-ntfs-3g.html
>> 
>> 
> There is also a package in the hipster repo:
> 
> system/file-system/ntfsprogs@2016.2.22,5.11-2016.0.0.2:20160730T020527Z 
> 
> 
> However, I didn't have much luck getting that one to work either.
> 
> Michael
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Michael Kruger]

On 09/25/2016 02:09 PM, Apostolos Syropoulos via openindiana-discuss wrote:


  Hello,

I kust wanted to check ntfs-3g and I downloaded and installed the packages from

http://jp-andre.pagesperso-orange.fr/openindiana-ntfs-3g.html



There is also a package in the hipster repo:

system/file-system/ntfsprogs@2016.2.22,5.11-2016.0.0.2:20160730T020527Z 



However, I didn't have much luck getting that one to work either.

Michael
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Apostolos Syropoulos via openindiana-discuss]

> > Does this work:
> ntfs-3g /dev/dsk/c4t0d0p1 /mnt
> 


# ntfs-3g /dev/rdsk/c4t0d0p1 /mnt
ntfs_attr_pread_i: ntfs_pread failed: Invalid argument
Failed to read NTFS $Bitmap: Invalid argument
The device '/devices/pci@0,0/pci1849,4396@13,2/storage@2/disk@0,0:r,raw' 
doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?


 A.S.
--
Apostolos Syropoulos
Xanthi, Greece

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ntfs-3g

[Thomas Wagner]

Does this work:
ntfs-3g /dev/dsk/c4t0d0p1 /mnt

Regards,
Thomas

On Sun, Sep 25, 2016 at 06:09:23PM +, Apostolos Syropoulos via 
openindiana-discuss wrote:
> 
> 
>  Hello,
> 
> I kust wanted to check ntfs-3g and I downloaded and installed the packages 
> from
> 
> http://jp-andre.pagesperso-orange.fr/openindiana-ntfs-3g.html
> 
> However, it seems that it is not working.
> 
> 
> # rmformat -l
> Looking for devices...
> 1. Logical Node: /dev/rdsk/c2t3d0p0
> Physical Node: /pci@0,0/pci1849,4391@11/cdrom@3,0
> Connected Device: HL-DT-ST DVDRAM GH24NSD1  LG00
> Device Type: DVD Reader/Writer
> Bus: 
> Size: 
> Label: 
> Access permissions: 
> 2. Logical Node: /dev/rdsk/c4t0d0p0
> Physical Node: /pci@0,0/pci1849,4396@13,2/storage@2/disk@0,0
> Connected Device: SanDisk  Cruzer Blade 1.00
> Device Type: Removable
> Bus: USB
> Size: 30,5 GB
> Label: 
> Access permissions: Medium is not write protected.
> # ntfs /dev/rdsk/c4t0d0p0 /mtn
> NTFS signature is missing.
> Failed to mount 
> '/devices/pci@0,0/pci1849,4396@13,2/storage@2/disk@0,0:q,raw': Invalid 
> argument
> The device '/devices/pci@0,0/pci1849,4396@13,2/storage@2/disk@0,0:q,raw' 
> doesn't seem to have a valid NTFS.
> Maybe the wrong device is used? Or the whole disk instead of a
> partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
> 
> Fdisk shows the following:
> 
> Partition   StatusType  Start   End   Length%
> =   ==  =   ===   ==   ===
> 1   ActiveIFS: NTFS 1  38903890100
> 
> The USB thumb disk has been formatted using a machine running Windows 7.
> 
> A.S.
> 
> 
> 
> --
> Apostolos Syropoulos
> Xanthi, Greece

-- 

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] NTFS-3G? (and FUSE)

[Ron Parker]

On Wed, Jun 22, 2011 at 11:24 AM, Gordon Ross gordon.w.r...@gmail.com wrote:
 BTW, if anyone is inclined to try building NTFS-3G, linked with the
 FUSE prototype I posted [1], I'd be curious to hear how it went.

Wish I'd seen your original post before now. Rolled my own about a
week ago. Haven't had anything to stress it too hard, but it seems
stable so far.

I'd be more than happy to give your solution a spin but it may be a
couple days before I can get to it. I'll try to report back.

-- 
Ron Parker

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] NTFS-3G

[Nikola M.]

On 04/26/11 12:20 PM, Robin Axelsson wrote:
 On 2011-04-23 16:06, Apostolos Syropoulos wrote:
 Hello,

 I have compiled ntfs-3g under OpenIndiana 148 and it works just fine.
 Also, I have made some patches and I have send them to the developers
 for
 review. If anyone wants to test the package, please send me an e-mail
 off-list.
 I was sitting for days trying to get it work on OSOL b111. I finally
 made it work but when I updated to 134 it stopped working again. The
 system just crashed hard
I had similar experience with fuse and ntfs-3g after upgrading to some
of the later Osol dev releases, too.
But I compiled fuse and then ntfs-3g again and everything started to
functioning like it was before. I use it now on OI and everything works
fine, like before.

It is even better if there is ntfs support with fuse inside some IPS
repository, soo after installing/upgrading to OpenIndiana, one can just
add that new IPS publisher and click-install it from packagemanager. Any
idea/support for making this new IPS repository with such (and other)
tools like that and making is available?

These are *_old_* instructions (I suppose there are newer ones now
somewhere):
http://hub.opensolaris.org/bin/view/Project+fuse/Installation
http://www.tuxera.com/community/ntfs-3g-download/
 pfexec pkg install gcc-dev sunstudioexpress SUNWmercurial
 cd /tmp
 mkdir ntfs
 cd ntfs
 wget -c http://dlc.sun.com/osol/on/downloads/current/SUNWonbld.i386.tar.bz2
 bzcat SUNWonbld.i386.tar.bz2 | tar -xvf -
 pfexec pkgadd -d onbld SUNWonbld
 export 
 PATH=/opt/SunStudioExpress/bin:/usr/bin:/usr/sfw/bin:/opt/onbld/bin/i386
 hg clone ssh://a...@hg.opensolaris.org/hg/fuse/libfuse
 hg clone ssh://a...@hg.opensolaris.org/hg/fuse/fusefs
 cd libfuse/
 make
 make install
 make pkg
 cd ../fusefs/kernel
 make
 make install
 make pkg
 pfexec /usr/sbin/pkgadd -d packages SUNWfusefs
 pfexec /usr/sbin/pkgadd -d ../../libfuse/packages SUNWlibfuse


 mkdir /tmp/ntfs/ntfs-3g
 cd /tmp/ntfs/ntfs-3g
 wget -c http://tuxera.com/opensource/ntfs-3g_ntfsprogs-2011.4.12.tgz
 tar xvzf ntfs-3g_ntfsprogs-2011.4.12
 cd ntfs-3g_ntfsprogs-2011.4.12
 ./configure
 make
 pfexec make install

To mount: pfexec ntfs-3g /dev/dsk/c7d0p1 /media/ntfs (or where partition is or 
mount point you like)
Or see with pfexec format and pfexec fdisk /dev/rdsk/_diskname_ what ntfs 
partition is. 
Same goes if Ntfs disk is plugged in USB port and works the same.

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] NTFS-3G

[Robin Axelsson]

On 2011-04-23 16:06, Apostolos Syropoulos wrote:

Hello,

I have compiled ntfs-3g under OpenIndiana 148 and it works just fine.
Also, I have made some patches and I have send them to the developers for
review. If anyone wants to test the package, please send me an e-mail
off-list.


Regards,

A.S.
  
--

Apostolos Syropoulos
Xanthi, Greece
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


Great job!
I was sitting for days trying to get it work on OSOL b111. I finally 
made it work but when I updated to 134 it stopped working again. The 
system just crashed hard whenever I tried to mount an NTFS volume (using 
mount ntfs-3g ). I even managed (after quite a bit of bickering) 
to compile the at the time latest version of fuse (I think it was 2.8.2) 
but that didn't help. It's as people say at the Opensolaris forums: 
ntfs-3g is fragile.
So if you have managed to make it work reliably, all I can say is 
congratulations! If you wish to share how you overcame the obstacles, 
that would be much appreciated.


Robin.



___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] NTFS-3G

[Guido Berhoerster]

* Damian Wojsław dam...@wojslaw.pl [2011-04-26 06:54]:
 Quoting Apostolos Syropoulos asyropou...@yahoo.com:
 
 Hello,
 
 I have compiled ntfs-3g under OpenIndiana 148 and it works just fine.
 Also, I have made some patches and I have send them to the developers for
 review. If anyone wants to test the package, please send me an e-mail
 off-list.
 
 
 Regards,
 
 A.S.
 
 Hi, I'd like to get this module.
 

There's a pretty recent version in SFE:
http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/SFEntfs-3g.spec?view=log

-- 
Guido Berhoerster

___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss