Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TODO #7

Open
namjaejeon opened this issue Jul 17, 2020 · 8 comments
Open

TODO #7

namjaejeon opened this issue Jul 17, 2020 · 8 comments

Comments

@namjaejeon
Copy link
Owner

namjaejeon commented Jul 17, 2020

  1. FITRIM ioctl
  2. NFS support
  3. fallocate
  4. symlink ?
@inste
Copy link
Contributor

inste commented Jul 24, 2020

To have 2 and 3 would be nice :)
Ready to test patches.

@namjaejeon
Copy link
Owner Author

Thanks for your opinion, I will try to work 2, 3 first if I make the time for these.
And I can't start working these jobs right now. I would be happy if someone try to implement it.

@piranna
Copy link

piranna commented Dec 12, 2020

Driver provided by Samsung did included symlink support by using reserved (unused) bits, although it's not standard and it got removed when merged in Linux kernel.

I would also be interested on having executable bit support using that reserved bits too.

@Erichorng
Copy link

Erichorng commented Nov 27, 2023

Hi! I'd like to ask a question.
I've recently encountered some issues when transferring large files using Samba, and it seems to be related to the lack of support for fallocate in exFAT.
According to the bellow discussion, I'm not sure if your plan refers to implementing the '--keep-size' functionality or the entire set of features.
From my understanding, to address the problem of transferring large files with Samba, it would be necessary to support at least the keep size flag and the default operation(mode=0).

https://lists.samba.org/archive/samba-technical/2020-December/136084.html

@namjaejeon
Copy link
Owner Author

@Erichorng Currently @YuezhangMo have been working valid-size support for exfat. I think that this patch fix your issue by speeding up ftruncate() of exfat. I will inform you if it is merged into exfat mainline.

@Erichorng
Copy link

Thank you for your response. Looking forward to it!

@namjaejeon
Copy link
Owner Author

namjaejeon commented Jan 2, 2024

@Erichorng Can you check if your problem is fixed with the following exfat branch ?

git clone https://github.com/namjaejeon/linux-exfat-oot/

@Erichorng
Copy link

@namjaejeon Thank you for the update.
I just tried it, and ftruncate on the new version of exFAT seems much faster! Also I found that it actually allocates disk space; it feels similar to the behavior of fallocate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants