> Sep 4 22:22:04 basil ntfs-3g[25041]: Hint
> /usr/lib/x86_64-linux-gnu/ntfs-3g/ntfs-plugin-801b.so: cannot open
> shared object file: No such file or directory
The tag 801b is not about system compression, but
for what Microsoft calls IO_REPARSE_TAG_APPEXECLINK.
AFAIK it is a trigger to
> Now I have been trying to figure out what each of the statements
> mean but have come up naught.
These are the parameters which define the layout of the data
in the ntfs partition. Most of them are meaningless to the end
user.
> For instance what does Device state: 11 mean or what does Volume
Jean-Pierre André wrote:
Jean-Pierre André wrote:
> I copy a directory tree from an ext4 partition to a NTFS one
> mounted with 'permissions' option using cp -r -p. For all files
> which have access permissions set to 755 their copies have
> access mask 700,
[...
Jean-Pierre André wrote:
> I copy a directory tree from an ext4 partition to a NTFS one
> mounted with 'permissions' option using cp -r -p. For all files
> which have access permissions set to 755 their copies have
> access mask 700,
[...]
Can you confirm this mat
> I copy a directory tree from an ext4 partition to a NTFS one
> mounted with 'permissions' option using cp -r -p. For all files
> which have access permissions set to 755 their copies have
> access mask 700,
You have probably enabled Posix ACLs, thus obeyed Windows
permissions. Then this behavio
> Mounting volume... $MFTMirr does not match $MFT (record 28).
Please open a specific ticket, this is unrelated to
the changelog issue.
Also, please attach to the report the output of :
sudo ntfsinfo -fm /dev/sdb1
> so it seems better to switch back following the AR releases, right?
This is not really a decision by me, I suppose you have
to follow some Debian guidelines.
I can only add that, if no distribution is interested in
the AR releases, the Tuxera versions will be less tested
before they are releas
> There were (is?) two kind of releases of ntfs-3g.
This is still the case.
> As I understood, Jean-Pierre abandoned the AR releases
Not at all. The only recent change is that Tuxera is not
referencing the AR releases any more, but they still exist
and they are a way to push fixes without being
László Böszörményi (GCS) wrote:
On Tue, Aug 29, 2017 at 12:09 PM, shirish शिरीष wrote:
On 29/08/2017, Jean-Pierre André wrote:
The full changelog is available on :
http://jp-andre.pagesperso-orange.fr/changelog.html
Aha,
The changelog at your end
http://jp-andre.pagesperso-orange.fr
shirish शिरीष wrote:
at bottom :-
On 29/08/2017, Jean-Pierre André wrote:
Upstream released a new version of ntfs-3g on March 28 STABLE Version
2017.3.23 (March 28, 2017)
Here are the release notes -
hanges to NTFS-3G:
Delegated processing of special reparse points to external plugins
Upstream released a new version of ntfs-3g on March 28 STABLE Version
2017.3.23 (March 28, 2017)
Here are the release notes -
hanges to NTFS-3G:
Delegated processing of special reparse points to external plugins
Allowed kernel cacheing by lowntfs-3g when not using Posix ACLs
Enabled
> # fstrim -v /media/my_data
> /media/my_data/: 104,2 GiB (111868387328 bytes) trimmed
> # fstrim -v /media/my_data
> /media/my_data/: 104,2 GiB (111868387328 bytes) trimmed
>
> Given that the current version of the ntfs-3g driver
> supports trimming, and given that fstrim ran twice, I
> expect th
Please see
http://tuxera.com/forum/viewtopic.php?f=2&t=31104&sid=26bd6fc5dd9dc86f0170051a4c8fffe8
Jean-Pierre
The tolerance to option -s was added to ntfs-3g-2015.3.14*
Because I can with the original ntfs-3g not work.
By telling us which ntfs-3g version you have a problem
with, we could route you around known problems with that
version. Also you bug report could be recorded and the
solution made available to other users having a similar
problem. The version is
df
/dev/sdc1 976759804 743605988 233153816 77% /media/Rb1TB
/dev/sdd1 1953477628 178017088 1775460540 10% /media/worker/RB2TB
This means both your devices are mounted :
/dev/sdc1 is mounted on /media/Rb1TB and
/dev/sdd1 is mounted on /media/worker/RB2TB
Then I start the disk-ma
in a root shell:
df
mount /media/sdb1 is not possible
umount /media/sdb1 is not possible only by disk-manager
Please tell what happens. There must be an error
message.
Also what is your exact mount command and what is
configured in /etc/fstab. If nothing is configured
in /etc/fstab, the
The metadata showed the segfault was caused by a bad
initialization of unused file records associated with a
missing safety check in ntfs-3g.
The attached patch adds the safety check, thus avoiding
the segfault.
Users having the same issue should start a chkdsk on
Windows, then use ntfswipe with
Thank you for posting detailed information about this issue.
As most of the data shown have invalid values, some record
is overflowing. See for instance the calls to ntfs_create()
and __ntfs_create(), whose arguments should not have different
values.
The error occurs in a sanity check while crea
Downgrading to 2012 version of ntfs-3g fixed it.
Using ntfs-3g version 2012.1.15AR.5 (or any version earlier
than 2012.1.1AR.7) on a system dual-booting with Windows 8
is very dangerous, as this version is not protected against
fast booting into Windows 8.
Did you disable the fast boot feature
> *** Error in `ntfsfix': free(): invalid pointer: 0x7f733989b678 ***
This is caused by retrying a failed umount before leaving
ntfsfix, and the attached patch should fix this bug.
The failed umount is a consequence of not being able to
write to /dev/sdk1, and IMHO this is caused by some
har
This issue has hopefully been fixed in ntfs-3g-2014.2.15AR.3,
now available.
Laszlo, can you set a proper subject line to this bug report ?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Thank you for the extra information.
In the meantime I have installed a version based on
kernel 2.6.35.14, and I can confirm your findings.
This version refuses to fallback on fuse protocol 7.8
(an old version which has all ntfs-3g needs except
Posix ACLs and ioctl support). It apparently requir
Thank you, Serge, for investigating the issue and
making a precise report.
Two more things I would like to know :
- which cpu are you using (32 or 64 bits) ?
- what were your ./configure options for compiling
ntfs-3g ? At least, what is the output of "ntfs-3g -help"
Regards
Jean-Pierre
--
To
* What was the outcome of this action?
this results in a a I/O error
Please post the exact error message.
Also, it might be useful you disclose the context by posting
the output of the commands below :
uname -a
ntfs-3g -help
cat /etc/fstab
mount
and, as root :
fdisk -l
ntfsfix -n /dev/sda1
Hi,
When invoked from usermap.c (as is done in function open_volume) the value of
the flags parameter seen by the implementation in security.c will be undefined
for any architecture with sizeof(unsigned long)!=sizeof(int). The declarations
in line 171 and 186 need to be amended to fix this.
Ye
Attached is a patch to add a new configure option
--enable-quarantined, so that distributors who do not
want to distribute developer-oriented programs and
non functional ones can easily do so. They may still
have to adapt their own packaging scripts (for added
symbolic links, etc.)
The proposed l
See
http://sourceforge.net/p/ntfs-3g/ntfs-3g/ci/c0287870e167a2289d85746125691cb665ee5c56/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Some comments I found on the Internet indicate this is a long
abandoned program that is non functional, so it should probably be
removed.
I agree.
The distributors were not supposed to enable the option
--enable-extras for enabling quarantined programs...
As some developers want to keep them a
This bug has been fixed in ntfs-3g-2014.2.15AR.1
Upgrading (or applying the patch in Message #30) is recommended
Jean-Pierre
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Niek Green wrote:
Hi,
I have attached a different variant of the patch, which
I prefer because it should have less overhead.
Can you try it also ?
Yep that one works too.
Great ! So that will be the one which I will promote upon
further testing.
Too bad, this is probably what I wanted, b
Hi again,
Niek Green wrote:
Hoi,
Thank you for testing. It confirms what I have found in the
meantime, and I have even found the cause.
I do not need the logs I asked, you can drop them.
Can you please try the attached patch over the latest
version 2013.1.13AR.4 ?
Done, no errors anymore.
Hi,
deb...@niek.gr wrote:
Hello,
What do you mean ? Is the issue un-repeatable, or did you switch
to an earlier version ?
I meant downgrading to the earlier version that is still in testing
(1:2013.1.13AR.1-2)
I haven't seen this problem with that version but when upgrading to
AR.4-2, the er
Hi,
ntfs-3g spitting out a lot of errors, rtorrent crashing with a SIGBUS
exception,
and the NTFS partition being corrupted.
Hmm. Probably bug introduced in 2013.1.13AR.4 through
either
http://sourceforge.net/p/ntfs-3g/ntfs-3g/ci/d2c7d40a2b494f9bf355c8bbe78c24fa16925f86/
or the subsequent
http
Hi,
This will be changed (along with most ntfsprogs utilities)
in future releases.
Regards
Jean-Pierre
Daniel Baumann wrote:
tag 741992 upstream
tag 741992 wontfix
thanks
On 03/20/2014 09:13 PM, Phillip Susi wrote:
The C and posix standards.
as said they don't cover --usage/--help/--versio
You might want to use the mount option "windows_names"
see http://www.tuxera.com/community/ntfs-3g-manual/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Well, I see that I have been tricked to anwer a five year
old topic... Nice way to discourage providing help.
And back to topic, this was probably copying from an
NTFS file system to ext3 or whatever, and copying
ownership and permissions from a file forced as being
owned by root to a user file f
You are using a very old Linux kernel, but which ntfs-3g
version are you using (type "ntfs-3g -help") ?
Did you get an error when mounting ? the option
"gid=fuse" should have been rejected as ntfs-3g requires
decimal values for uid and gid.
Did you define the user mapping (in .NTFS-3G) ?
What m
Hi,
Hi, It's a windows 7 fresh install, the system was not hibernated when I
had these problems, ntfscheck/info said about some unsupported flags
Do you remember which flags ? Could be "dirty" meaning
a partition previously improperly unmounted (for power
failure, etc.)
It's an hard disk not
Hi,
The errors exhibited by chkdsk are typical of what
happens when two OS access a partition with one of
them not being aware of the changes done by the
other one.
A typical situation for this to happen is updating on
Linux a partition mounted on Windows while the
latter is hibernated. On Windo
Hi,
problematic version: 1:2012.1.15AR.5-2.1
backported working version: 1:2013.1.13AR.1-2
Can you please confirm which one is the version
with suspected bad behavior ?
If you fixed the file system by using chkdsk, can
you please post its log, which you can find in
mountpoint/'System Volu
Hi,
EVERY user's directory in Windows 7
contains an "AppData" folder. It is impossible to identify
which is which without more information.
You can decline to reply on ambiguous files or
directories, you will be asked later on another
file or directory with the same owner.
Another possibility
Hi!
With ntfs-3g I can put "?" in filenames which is allowed with Linux (and
MacOSX btw) but NOT with Windows, as Windows confuses that symbol with
the joker which replaces a random character.
I think ntfs-3g should respect the Windows file System constrainsts to
make it coherent with Windows.
Hi,
I have an fstab entry like:
UUID=24F0E2D4F0E2AB6E /mnt/ata-Maxtor_6V250F0_V593GLTG ntfs-3g
no_def_opts,windows_names,noatime,uid=1000,gid=1000,noauto,allow_other,nofail,hide_hid_files
0 2
Do not use 2 as the last option : this means requiring
a file system check, but there is no known op
I had a failing disk and wanted to put things on a new disk that
happens to be smaller. I started by creating a clone, and then
tried to restore it on the new disk.
Currently resizing + cloning in a single step is not possible.
Restoring from a compact image + resizing is not technically
feasa
This appears to be the same as bug #685551, however, that bug is marked as
fixed in the version of ntfs-3g I am using, yet I am still experiencing this
bug.
Which bug ?
The loops in the Windows tree are a decision from Microsoft.
Please give an example of a problem this causes to you
and which
46 matches
Mail list logo
