Does Linux have system calls to access all the features of the file systems it supports?
Linux supports many file systems (for example: ext3, NTFS, FAT32, etc.).
The following diagram shows how Linux allows a process to access files:
So assume that a process called the read() system call to read a file, what will happen is that the VFS layer will be accessed, and the VFS layer will decide which file system driver to access based on the file system of the partition that the file to be read resides on.
Linux provides many system calls to access files (for example: read(), write(), rename(), etc.).
Now read() and write() and rename() work on all the file systems that Linux supports.
But there are specific features that exist only on some file systems while not existing on others. For example: on a NTFS file system, you can set the Archive bit for a file, while this can't be done on an ext3 file system.
Now my question is, does Linux have system calls to access all the features of the file systems it supports? for example: does Linux have a system call to set the Archive bit for a file on a NTFS file system?
linux filesystems
asked Mar 13 at 20:37
user341642user341642
562
add a comment |
Linux supports many file systems (for example: ext3, NTFS, FAT32, etc.).
The following diagram shows how Linux allows a process to access files:
So assume that a process called the read() system call to read a file, what will happen is that the VFS layer will be accessed, and the VFS layer will decide which file system driver to access based on the file system of the partition that the file to be read resides on.
Linux provides many system calls to access files (for example: read(), write(), rename(), etc.).
Now read() and write() and rename() work on all the file systems that Linux supports.
But there are specific features that exist only on some file systems while not existing on others. For example: on a NTFS file system, you can set the Archive bit for a file, while this can't be done on an ext3 file system.
Now my question is, does Linux have system calls to access all the features of the file systems it supports? for example: does Linux have a system call to set the Archive bit for a file on a NTFS file system?
linux filesystems
asked Mar 13 at 20:37
user341642user341642
562
add a comment |
Linux supports many file systems (for example: ext3, NTFS, FAT32, etc.).
The following diagram shows how Linux allows a process to access files:
So assume that a process called the read() system call to read a file, what will happen is that the VFS layer will be accessed, and the VFS layer will decide which file system driver to access based on the file system of the partition that the file to be read resides on.
Linux provides many system calls to access files (for example: read(), write(), rename(), etc.).
Now read() and write() and rename() work on all the file systems that Linux supports.
But there are specific features that exist only on some file systems while not existing on others. For example: on a NTFS file system, you can set the Archive bit for a file, while this can't be done on an ext3 file system.
Now my question is, does Linux have system calls to access all the features of the file systems it supports? for example: does Linux have a system call to set the Archive bit for a file on a NTFS file system?
linux filesystems
asked Mar 13 at 20:37
user341642user341642
562
Linux supports many file systems (for example: ext3, NTFS, FAT32, etc.).
The following diagram shows how Linux allows a process to access files:
So assume that a process called the read() system call to read a file, what will happen is that the VFS layer will be accessed, and the VFS layer will decide which file system driver to access based on the file system of the partition that the file to be read resides on.
Linux provides many system calls to access files (for example: read(), write(), rename(), etc.).
Now read() and write() and rename() work on all the file systems that Linux supports.
But there are specific features that exist only on some file systems while not existing on others. For example: on a NTFS file system, you can set the Archive bit for a file, while this can't be done on an ext3 file system.
Now my question is, does Linux have system calls to access all the features of the file systems it supports? for example: does Linux have a system call to set the Archive bit for a file on a NTFS file system?
linux filesystems
linux filesystems
asked Mar 13 at 20:37
user341642user341642
562
asked Mar 13 at 20:37
user341642user341642
562
asked Mar 13 at 20:37
user341642user341642
562
asked Mar 13 at 20:37
user341642user341642
562
asked Mar 13 at 20:37
user341642user341642
562
562
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
does Linux have a system call to set the Archive bit for a file on a NTFS file system?
For this particular case, the ntfs-3g driver exports the file attributes via extended attributes, see Can I set the "Archive" bit on a file on NTFS on Linux?
The (V)FAT file system has the similar file attributes, but it uses an ioctl() function to access them, see ioctl_fat(2). (ioctl() is a sort of a multipurpose system call, used for all kinds of device specific stuff that don't warrant a real system call.)
Now my question is, does Linux have system calls to access all the features of the file systems it supports?
It's hard to answer for sure, but there has been at least one example of the opposite. ext4 internally supports a "birth time" timestamp for files (like, a real creation time, unlike ctime that changes on inode modification). But even though ext4 is the "standard" filesystem, for a long time, there was no system call to access the birth time.
It should be supported now, with the statx() system call added in Linux 4.11, in April 2017.
Related:
- Birth is empty on ext4
- A number of articles on lwn.net about statx, including e.g. statx() v3
answered Mar 13 at 20:52
ilkkachuilkkachu
62.4k10103179
3
ntfs != fat. At least the kernel version of ntfs does NOT have any way to set or get the archive flag, though its headers define it. Only the fuse based ntfs-3g seems to support it (via extended attributes, not special ioctls).
– Uncle Billy
Mar 13 at 21:04
This isn’t directly related to the question, but as a complement to your mention ofstatx, it’s now supported in the C library and in the latest version of coreutils which was released a few days ago.
– Stephen Kitt
Mar 13 at 21:05
@UncleBilly, d'oh, apparently I can't read, but just automatically thought of (v)fat. Thanks for noticing that, I'll see if I can find a more appropriate reference.
– ilkkachu
Mar 13 at 21:13
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506160%2fdoes-linux-have-system-calls-to-access-all-the-features-of-the-file-systems-it-s%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
does Linux have a system call to set the Archive bit for a file on a NTFS file system?
For this particular case, the ntfs-3g driver exports the file attributes via extended attributes, see Can I set the "Archive" bit on a file on NTFS on Linux?
The (V)FAT file system has the similar file attributes, but it uses an ioctl() function to access them, see ioctl_fat(2). (ioctl() is a sort of a multipurpose system call, used for all kinds of device specific stuff that don't warrant a real system call.)
Now my question is, does Linux have system calls to access all the features of the file systems it supports?
It's hard to answer for sure, but there has been at least one example of the opposite. ext4 internally supports a "birth time" timestamp for files (like, a real creation time, unlike ctime that changes on inode modification). But even though ext4 is the "standard" filesystem, for a long time, there was no system call to access the birth time.
It should be supported now, with the statx() system call added in Linux 4.11, in April 2017.
Related:
- Birth is empty on ext4
- A number of articles on lwn.net about statx, including e.g. statx() v3
answered Mar 13 at 20:52
ilkkachuilkkachu
62.4k10103179
3
ntfs != fat. At least the kernel version of ntfs does NOT have any way to set or get the archive flag, though its headers define it. Only the fuse based ntfs-3g seems to support it (via extended attributes, not special ioctls).
– Uncle Billy
Mar 13 at 21:04
This isn’t directly related to the question, but as a complement to your mention ofstatx, it’s now supported in the C library and in the latest version of coreutils which was released a few days ago.
– Stephen Kitt
Mar 13 at 21:05
@UncleBilly, d'oh, apparently I can't read, but just automatically thought of (v)fat. Thanks for noticing that, I'll see if I can find a more appropriate reference.
– ilkkachu
Mar 13 at 21:13
add a comment |
does Linux have a system call to set the Archive bit for a file on a NTFS file system?
For this particular case, the ntfs-3g driver exports the file attributes via extended attributes, see Can I set the "Archive" bit on a file on NTFS on Linux?
The (V)FAT file system has the similar file attributes, but it uses an ioctl() function to access them, see ioctl_fat(2). (ioctl() is a sort of a multipurpose system call, used for all kinds of device specific stuff that don't warrant a real system call.)
Now my question is, does Linux have system calls to access all the features of the file systems it supports?
It's hard to answer for sure, but there has been at least one example of the opposite. ext4 internally supports a "birth time" timestamp for files (like, a real creation time, unlike ctime that changes on inode modification). But even though ext4 is the "standard" filesystem, for a long time, there was no system call to access the birth time.
It should be supported now, with the statx() system call added in Linux 4.11, in April 2017.
Related:
- Birth is empty on ext4
- A number of articles on lwn.net about statx, including e.g. statx() v3
answered Mar 13 at 20:52
ilkkachuilkkachu
62.4k10103179
3
ntfs != fat. At least the kernel version of ntfs does NOT have any way to set or get the archive flag, though its headers define it. Only the fuse based ntfs-3g seems to support it (via extended attributes, not special ioctls).
– Uncle Billy
Mar 13 at 21:04
This isn’t directly related to the question, but as a complement to your mention ofstatx, it’s now supported in the C library and in the latest version of coreutils which was released a few days ago.
– Stephen Kitt
Mar 13 at 21:05
@UncleBilly, d'oh, apparently I can't read, but just automatically thought of (v)fat. Thanks for noticing that, I'll see if I can find a more appropriate reference.
– ilkkachu
Mar 13 at 21:13
add a comment |
does Linux have a system call to set the Archive bit for a file on a NTFS file system?
For this particular case, the ntfs-3g driver exports the file attributes via extended attributes, see Can I set the "Archive" bit on a file on NTFS on Linux?
The (V)FAT file system has the similar file attributes, but it uses an ioctl() function to access them, see ioctl_fat(2). (ioctl() is a sort of a multipurpose system call, used for all kinds of device specific stuff that don't warrant a real system call.)
Now my question is, does Linux have system calls to access all the features of the file systems it supports?
It's hard to answer for sure, but there has been at least one example of the opposite. ext4 internally supports a "birth time" timestamp for files (like, a real creation time, unlike ctime that changes on inode modification). But even though ext4 is the "standard" filesystem, for a long time, there was no system call to access the birth time.
It should be supported now, with the statx() system call added in Linux 4.11, in April 2017.
Related:
- Birth is empty on ext4
- A number of articles on lwn.net about statx, including e.g. statx() v3
answered Mar 13 at 20:52
ilkkachuilkkachu
62.4k10103179
does Linux have a system call to set the Archive bit for a file on a NTFS file system?
For this particular case, the ntfs-3g driver exports the file attributes via extended attributes, see Can I set the "Archive" bit on a file on NTFS on Linux?
The (V)FAT file system has the similar file attributes, but it uses an ioctl() function to access them, see ioctl_fat(2). (ioctl() is a sort of a multipurpose system call, used for all kinds of device specific stuff that don't warrant a real system call.)
Now my question is, does Linux have system calls to access all the features of the file systems it supports?
It's hard to answer for sure, but there has been at least one example of the opposite. ext4 internally supports a "birth time" timestamp for files (like, a real creation time, unlike ctime that changes on inode modification). But even though ext4 is the "standard" filesystem, for a long time, there was no system call to access the birth time.
It should be supported now, with the statx() system call added in Linux 4.11, in April 2017.
Related:
- Birth is empty on ext4
- A number of articles on lwn.net about statx, including e.g. statx() v3
answered Mar 13 at 20:52
ilkkachuilkkachu
62.4k10103179
edited Mar 13 at 21:16
answered Mar 13 at 20:52
ilkkachuilkkachu
62.4k10103179
answered Mar 13 at 20:52
ilkkachuilkkachu
62.4k10103179
answered Mar 13 at 20:52
ilkkachuilkkachu
62.4k10103179
62.4k10103179
3
ntfs != fat. At least the kernel version of ntfs does NOT have any way to set or get the archive flag, though its headers define it. Only the fuse based ntfs-3g seems to support it (via extended attributes, not special ioctls).
– Uncle Billy
Mar 13 at 21:04
This isn’t directly related to the question, but as a complement to your mention ofstatx, it’s now supported in the C library and in the latest version of coreutils which was released a few days ago.
– Stephen Kitt
Mar 13 at 21:05
@UncleBilly, d'oh, apparently I can't read, but just automatically thought of (v)fat. Thanks for noticing that, I'll see if I can find a more appropriate reference.
– ilkkachu
Mar 13 at 21:13
add a comment |
3
ntfs != fat. At least the kernel version of ntfs does NOT have any way to set or get the archive flag, though its headers define it. Only the fuse based ntfs-3g seems to support it (via extended attributes, not special ioctls).
– Uncle Billy
Mar 13 at 21:04
This isn’t directly related to the question, but as a complement to your mention ofstatx, it’s now supported in the C library and in the latest version of coreutils which was released a few days ago.
– Stephen Kitt
Mar 13 at 21:05
@UncleBilly, d'oh, apparently I can't read, but just automatically thought of (v)fat. Thanks for noticing that, I'll see if I can find a more appropriate reference.
– ilkkachu
Mar 13 at 21:13
3
3
ntfs != fat. At least the kernel version of ntfs does NOT have any way to set or get the archive flag, though its headers define it. Only the fuse based ntfs-3g seems to support it (via extended attributes, not special ioctls).
– Uncle Billy
Mar 13 at 21:04
ntfs != fat. At least the kernel version of ntfs does NOT have any way to set or get the archive flag, though its headers define it. Only the fuse based ntfs-3g seems to support it (via extended attributes, not special ioctls).
– Uncle Billy
Mar 13 at 21:04
This isn’t directly related to the question, but as a complement to your mention of
statx, it’s now supported in the C library and in the latest version of coreutils which was released a few days ago.– Stephen Kitt
Mar 13 at 21:05
This isn’t directly related to the question, but as a complement to your mention of
statx, it’s now supported in the C library and in the latest version of coreutils which was released a few days ago.– Stephen Kitt
Mar 13 at 21:05
@UncleBilly, d'oh, apparently I can't read, but just automatically thought of (v)fat. Thanks for noticing that, I'll see if I can find a more appropriate reference.
– ilkkachu
Mar 13 at 21:13
@UncleBilly, d'oh, apparently I can't read, but just automatically thought of (v)fat. Thanks for noticing that, I'll see if I can find a more appropriate reference.
– ilkkachu
Mar 13 at 21:13
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506160%2fdoes-linux-have-system-calls-to-access-all-the-features-of-the-file-systems-it-s%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
