What's new

3.0.0.4.380_7266 - NTFS MFT expansion errors

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Alystair

New Around Here
This also happens in previous firmware versions... been getting frequent issues on a large shared drive, causing the shares to all become 'read-only'. Hopefully Merlin can convince Asus nag Tuxera to fix this as it's quite detrimental :^)

Code:
Feb 28 19:18:38 kernel: tntfs error (device sda1, pid 23263): ntfs_mft_record_alloc(): Failed to extend mft data allocation.
Feb 28 19:18:38 kernel: tntfs error (device sda1, pid 23263): ntfs_create_helper(): Failed to allocate a new on-disk inode (error 95).
Feb 28 19:18:38 kernel: tntfs error (device sda1, pid 23263): ntfs_create_helper(): Failed (error 95).
Feb 28 19:18:38 kernel: tntfs error (device sda1, pid 23263): ntfs_mft_data_extend_allocation_nolock(): Not enough space in this mft record to accommodate extended mft data attribute extent.  Cannot handle this yet.
Feb 28 19:18:38 kernel: tntfs error (device sda1, pid 23263): ntfs_mft_record_alloc(): Failed to extend mft data allocation.
Feb 28 19:18:38 kernel: tntfs error (device sda1, pid 23263): ntfs_create_helper(): Failed to allocate a new on-disk inode (error 95).

A potential workaround is using UltraDefrag (free) to optimize the MFT. I'll see if this solves the problem and report back.
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top