crazycodemonkey wrote:
Tried with:
ntfs-3g_ntfsprogs-2017.3.23AR.2
ntfs-3g_ntfsprogs-2017.3.23AR.3
but I get the same error.
Then, I will probably not be able to fix it without having
a metadata copy of your partition. The metadata copy
holds no user data, however the file names are visible
and this may be a problem.
To make a metadata copy, run as root :
ntfsclone -mst -O - the-partition | gzip > metadata.gz
The partition (/dev/something) must be unmounted
Warning : the metadata.gz could be big.
Anything else I could try before I end up running chkdsk?
This error is an indication of excessive fragmentation, and
chkdsk will probably not do much about it.
What you need is a defragmenter.
Jean-Pierre
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, 29. October 2018 13:54, Jean-Pierre André
<jean-pierre.an...@wanadoo.fr> wrote:
Hi,
crazycodemonkey wrote:
Thanks for the hint.
I just downloaded
http://jp-andre.pagesperso-orange.fr/ntfs-3g_ntfsprogs-2017.3.23AR.2.tgz
and build it in the /tmp directory
I was able to mount a dummy ntfs partition/image using:
sudo ./ntfs-3g_ntfsprogs-2017.3.23AR.2/src/ntfs-3g ntfs.img /tmp/mnt
And it seems to work so far.
Good news, assuming your test partition was in the
condition for the issue to show.
Is it ok to do the same for my actual partition?
I would expect so. First make a try without installing :
sudo ./ntfs-3g_ntfsprogs-2017.3.23AR.2/src/ntfs-3g the-partition the-mountpoint
Or will the new ntfs-3g try to use some old libs or something like that? (so
new stuff gets mixed with old)
It is unlikely ntfs-3g uses a wrong libntfs-3g, as the lib
identification changes along with the version.
However please note that the default install directory
is probably not the one which your distribution
recommends, so your current libntfs-3g will not be
overwritten. Unless you have other packages relying on
your current lib, you should first delete the current
package.
Regards
Jean-Pierre
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, 28. October 2018 17:55,
Jean-Pierre André jean-pierre.an...@wanadoo.fr wrote:
crazycodemonkey via ntfs-3g-devel wrote:
Hi guys,
I have an ntfs partition which worked fine before.
Now when I try to create a new file on that partition I get the error:
"No free mft record for $MFT: No space left on device"
When I delete one file from the partition, I'm able to create a new one.
A bug occurring while extending the MFT in some special
situation was fixed in ntfs-3g-2017.3.23AR.2 and your issue
may be solved by upgrading.
Some distributions have packages available for ntfs-3g-2017.3.23AR.2
and ntfs-3g-2017.3.23AR.3 otherwise you have to compile
your own from source :
http://jp-andre.pagesperso-orange.fr/advanced-ntfs-3g.html#download
If I got it correctly the MFT should have at least 12,2% of the
partition's size.
That would be some GBs for me. Atm $MFT is about 411MB.
So I don't get it, why the MFT can't increase in size although there
is enough free space.
find tells me I have about 419811 files/directories on that partition.
using:
kernel: 4.9.0-6-amd64
ntfs-3g 2016.2.22AR.1
_______________________________________________
ntfs-3g-devel mailing list
ntfs-3g-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
