How does the sequence of inode numbers work? Can I expect consistency across identical installs on different...
How to save money by shopping at a variety of grocery stores?
How do I get my neighbour to stop disturbing with loud music?
In Endgame, wouldn't Stark have remembered Hulk busting out of the stairwell?
Cheap oscilloscope showing 16 MHz square wave
How to understand payment due date for credit card?
Understanding data transmission rates over copper wire
Lob Logical Read and lob read-ahead reads in NCCI
Resources to learn about firearms?
Which is the correct version of Mussorgsky's Pictures at an Exhibition?
Are sweatpants frowned upon on flights?
math mode in ticks ( tikzpicture )
Welche normative Autorität hat der Duden? / What's the normative authority of the Duden?
Small RAM 4 KB on the early Apple II?
Storing milk for long periods of time
Find the logic in first 2 statements to give the answer for the third statement
Can I leave a large suitcase at TPE during a 4-hour layover, and pick it up 4.5 days later when I come back to TPE on my way to Taipei downtown?
What am I looking at here at Google Sky?
'Horseshoes' for Deer?
How can I portray a character with no fear of death, without them sounding utterly bored?
IList<T> implementation
How to differentiate between two people with the same name in a story?
Ask one verbal question to figure out who is blind and who is mute among three persons
Necessity of tenure for lifetime academic research
Padding a column of lists
How does the sequence of inode numbers work? Can I expect consistency across identical installs on different computers?
what is inode for, in FreeBSD or SolarisHow are large directories stored (one inode or many?)Moving a file inside the same File Systembtrfs same inode numberHow can I create files in the directory to have inodes allocated to files with non-sequential inode numbers?How does linux store the mapping folder -> file_name -> inode?How a mount point directory entry is different from an usual directory entry in a filesystem
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have 3 computers, A, B, and C, and I perform identical operating system and software installations on them. For any specific file on A, can I expect that same file on B and C to have the same inode number for its instance of that file?
Our intrusion detection system is set up by acquiring an initial file system image from A and then using that same file system image to do future comparisons against A, B, and C. I am new to the program, but it seems that this has worked in the past.
I don't know how the inode number sequencing works, so I'm guessing it just starts at 1 and counts up for each file, or something similar. If that's the case, that's probably why file inode numbers have been consistent even across computers for us in the past - the same files were created in the same order. Though I'm not sure if we can always count on that.
However, now I am getting notifications of a few files changed, and for the first file I am looking into it is only the file inode number which has changed. I think someone reinstalled the operating system and software on the computer with the notifications.
Can file inode numbers be counted on to be the same across identical OS/software installs on different computers (or sequential re-installs on the same computer)?
If I were to acquire a new file system image from either A, B, or C, can I expect that to fix my "problem" (not even sure if it's a problem)?
I generally have access to only 1 or 2 of the computers at a time, so I cannot inspect A or C right now, and I do not know what their report would look like. I only know that the inode number of at least 1 file on computer B is not what was expected.
In this case, the operating system is QNX 6. For file system type, mount tells me that the /dev/hd file's are "on / type qnx4"... so file system type qnx4? I guess qnx has its own file system type? I didn't realize that. Or maybe that's no accurate. Other commands for checking file system type do not seem to exist on the computer.
filesystems inode qnx
asked 4 hours ago
AaronAaron
1284 bronze badges
add a comment |
I have 3 computers, A, B, and C, and I perform identical operating system and software installations on them. For any specific file on A, can I expect that same file on B and C to have the same inode number for its instance of that file?
Our intrusion detection system is set up by acquiring an initial file system image from A and then using that same file system image to do future comparisons against A, B, and C. I am new to the program, but it seems that this has worked in the past.
I don't know how the inode number sequencing works, so I'm guessing it just starts at 1 and counts up for each file, or something similar. If that's the case, that's probably why file inode numbers have been consistent even across computers for us in the past - the same files were created in the same order. Though I'm not sure if we can always count on that.
However, now I am getting notifications of a few files changed, and for the first file I am looking into it is only the file inode number which has changed. I think someone reinstalled the operating system and software on the computer with the notifications.
Can file inode numbers be counted on to be the same across identical OS/software installs on different computers (or sequential re-installs on the same computer)?
If I were to acquire a new file system image from either A, B, or C, can I expect that to fix my "problem" (not even sure if it's a problem)?
I generally have access to only 1 or 2 of the computers at a time, so I cannot inspect A or C right now, and I do not know what their report would look like. I only know that the inode number of at least 1 file on computer B is not what was expected.
In this case, the operating system is QNX 6. For file system type, mount tells me that the /dev/hd file's are "on / type qnx4"... so file system type qnx4? I guess qnx has its own file system type? I didn't realize that. Or maybe that's no accurate. Other commands for checking file system type do not seem to exist on the computer.
filesystems inode qnx
asked 4 hours ago
AaronAaron
1284 bronze badges
Related: How to keep i-node consistent across separate Filesystems
– Kusalananda♦
4 hours ago
Even more related: Making bit identical ext2 filesystems
– Kusalananda♦
4 hours ago
It would not be enough to know what Unix you use, it would also be necessary to know what type of filesystem you use. I know of no common filesystem on Unix that use sequential numbering of inodes. I also don't quite know what you mean by "sequential". Do you mean sequentially stored on disk or sequentially created? Have a look at the inodes of the files in few large directories, on the systems I use, some may look sequential, but there are often big jumps. In general, inodes between devices can not be expected to refer to the same files.
– Kusalananda♦
4 hours ago
1
1) Will add to question. 2) By sequential, I mean the inode numbers for sequentially created files. For example, I did a testecho test1>test1thenecho test2>test2, and test2's inode number was 1 higher than test1's (ie: file1's: 1234, file2's: 1235) @Kusalananda Also, I will look into the links you provided. Thank you.
– Aaron
3 hours ago
I'm not using QNX so I cannot give you an answer, but IMHO it would be very foolish to rely on that. Something trivial like the installer parallelizing some ops, as in foo2>log1 | bar 2>log2may completely defeat it, since there's no telling in which orderlog1andlog2will be created (trying that withwatch(1)show that the two files will swap inodes quite frequently, the more busy the system, the faster ;-)).
– mosvy
25 mins ago
add a comment |
I have 3 computers, A, B, and C, and I perform identical operating system and software installations on them. For any specific file on A, can I expect that same file on B and C to have the same inode number for its instance of that file?
Our intrusion detection system is set up by acquiring an initial file system image from A and then using that same file system image to do future comparisons against A, B, and C. I am new to the program, but it seems that this has worked in the past.
I don't know how the inode number sequencing works, so I'm guessing it just starts at 1 and counts up for each file, or something similar. If that's the case, that's probably why file inode numbers have been consistent even across computers for us in the past - the same files were created in the same order. Though I'm not sure if we can always count on that.
However, now I am getting notifications of a few files changed, and for the first file I am looking into it is only the file inode number which has changed. I think someone reinstalled the operating system and software on the computer with the notifications.
Can file inode numbers be counted on to be the same across identical OS/software installs on different computers (or sequential re-installs on the same computer)?
If I were to acquire a new file system image from either A, B, or C, can I expect that to fix my "problem" (not even sure if it's a problem)?
I generally have access to only 1 or 2 of the computers at a time, so I cannot inspect A or C right now, and I do not know what their report would look like. I only know that the inode number of at least 1 file on computer B is not what was expected.
In this case, the operating system is QNX 6. For file system type, mount tells me that the /dev/hd file's are "on / type qnx4"... so file system type qnx4? I guess qnx has its own file system type? I didn't realize that. Or maybe that's no accurate. Other commands for checking file system type do not seem to exist on the computer.
filesystems inode qnx
asked 4 hours ago
AaronAaron
1284 bronze badges
I have 3 computers, A, B, and C, and I perform identical operating system and software installations on them. For any specific file on A, can I expect that same file on B and C to have the same inode number for its instance of that file?
Our intrusion detection system is set up by acquiring an initial file system image from A and then using that same file system image to do future comparisons against A, B, and C. I am new to the program, but it seems that this has worked in the past.
I don't know how the inode number sequencing works, so I'm guessing it just starts at 1 and counts up for each file, or something similar. If that's the case, that's probably why file inode numbers have been consistent even across computers for us in the past - the same files were created in the same order. Though I'm not sure if we can always count on that.
However, now I am getting notifications of a few files changed, and for the first file I am looking into it is only the file inode number which has changed. I think someone reinstalled the operating system and software on the computer with the notifications.
Can file inode numbers be counted on to be the same across identical OS/software installs on different computers (or sequential re-installs on the same computer)?
If I were to acquire a new file system image from either A, B, or C, can I expect that to fix my "problem" (not even sure if it's a problem)?
I generally have access to only 1 or 2 of the computers at a time, so I cannot inspect A or C right now, and I do not know what their report would look like. I only know that the inode number of at least 1 file on computer B is not what was expected.
In this case, the operating system is QNX 6. For file system type, mount tells me that the /dev/hd file's are "on / type qnx4"... so file system type qnx4? I guess qnx has its own file system type? I didn't realize that. Or maybe that's no accurate. Other commands for checking file system type do not seem to exist on the computer.
filesystems inode qnx
filesystems inode qnx
asked 4 hours ago
AaronAaron
1284 bronze badges
asked 4 hours ago
AaronAaron
1284 bronze badges
edited 3 hours ago
Aaron
asked 4 hours ago
AaronAaron
1284 bronze badges
asked 4 hours ago
AaronAaron
1284 bronze badges
asked 4 hours ago
AaronAaron
1284 bronze badges
1284 bronze badges
Related: How to keep i-node consistent across separate Filesystems
– Kusalananda♦
4 hours ago
Even more related: Making bit identical ext2 filesystems
– Kusalananda♦
4 hours ago
It would not be enough to know what Unix you use, it would also be necessary to know what type of filesystem you use. I know of no common filesystem on Unix that use sequential numbering of inodes. I also don't quite know what you mean by "sequential". Do you mean sequentially stored on disk or sequentially created? Have a look at the inodes of the files in few large directories, on the systems I use, some may look sequential, but there are often big jumps. In general, inodes between devices can not be expected to refer to the same files.
– Kusalananda♦
4 hours ago
1
1) Will add to question. 2) By sequential, I mean the inode numbers for sequentially created files. For example, I did a testecho test1>test1thenecho test2>test2, and test2's inode number was 1 higher than test1's (ie: file1's: 1234, file2's: 1235) @Kusalananda Also, I will look into the links you provided. Thank you.
– Aaron
3 hours ago
I'm not using QNX so I cannot give you an answer, but IMHO it would be very foolish to rely on that. Something trivial like the installer parallelizing some ops, as in foo2>log1 | bar 2>log2may completely defeat it, since there's no telling in which orderlog1andlog2will be created (trying that withwatch(1)show that the two files will swap inodes quite frequently, the more busy the system, the faster ;-)).
– mosvy
25 mins ago
add a comment |
Related: How to keep i-node consistent across separate Filesystems
– Kusalananda♦
4 hours ago
Even more related: Making bit identical ext2 filesystems
– Kusalananda♦
4 hours ago
It would not be enough to know what Unix you use, it would also be necessary to know what type of filesystem you use. I know of no common filesystem on Unix that use sequential numbering of inodes. I also don't quite know what you mean by "sequential". Do you mean sequentially stored on disk or sequentially created? Have a look at the inodes of the files in few large directories, on the systems I use, some may look sequential, but there are often big jumps. In general, inodes between devices can not be expected to refer to the same files.
– Kusalananda♦
4 hours ago
1
1) Will add to question. 2) By sequential, I mean the inode numbers for sequentially created files. For example, I did a testecho test1>test1thenecho test2>test2, and test2's inode number was 1 higher than test1's (ie: file1's: 1234, file2's: 1235) @Kusalananda Also, I will look into the links you provided. Thank you.
– Aaron
3 hours ago
I'm not using QNX so I cannot give you an answer, but IMHO it would be very foolish to rely on that. Something trivial like the installer parallelizing some ops, as in foo2>log1 | bar 2>log2may completely defeat it, since there's no telling in which orderlog1andlog2will be created (trying that withwatch(1)show that the two files will swap inodes quite frequently, the more busy the system, the faster ;-)).
– mosvy
25 mins ago
Related: How to keep i-node consistent across separate Filesystems
– Kusalananda♦
4 hours ago
Related: How to keep i-node consistent across separate Filesystems
– Kusalananda♦
4 hours ago
Even more related: Making bit identical ext2 filesystems
– Kusalananda♦
4 hours ago
Even more related: Making bit identical ext2 filesystems
– Kusalananda♦
4 hours ago
It would not be enough to know what Unix you use, it would also be necessary to know what type of filesystem you use. I know of no common filesystem on Unix that use sequential numbering of inodes. I also don't quite know what you mean by "sequential". Do you mean sequentially stored on disk or sequentially created? Have a look at the inodes of the files in few large directories, on the systems I use, some may look sequential, but there are often big jumps. In general, inodes between devices can not be expected to refer to the same files.
– Kusalananda♦
4 hours ago
It would not be enough to know what Unix you use, it would also be necessary to know what type of filesystem you use. I know of no common filesystem on Unix that use sequential numbering of inodes. I also don't quite know what you mean by "sequential". Do you mean sequentially stored on disk or sequentially created? Have a look at the inodes of the files in few large directories, on the systems I use, some may look sequential, but there are often big jumps. In general, inodes between devices can not be expected to refer to the same files.
– Kusalananda♦
4 hours ago
1
1
1) Will add to question. 2) By sequential, I mean the inode numbers for sequentially created files. For example, I did a test
echo test1>test1 then echo test2>test2, and test2's inode number was 1 higher than test1's (ie: file1's: 1234, file2's: 1235) @Kusalananda Also, I will look into the links you provided. Thank you.– Aaron
3 hours ago
1) Will add to question. 2) By sequential, I mean the inode numbers for sequentially created files. For example, I did a test
echo test1>test1 then echo test2>test2, and test2's inode number was 1 higher than test1's (ie: file1's: 1234, file2's: 1235) @Kusalananda Also, I will look into the links you provided. Thank you.– Aaron
3 hours ago
I'm not using QNX so I cannot give you an answer, but IMHO it would be very foolish to rely on that. Something trivial like the installer parallelizing some ops, as in foo
2>log1 | bar 2>log2 may completely defeat it, since there's no telling in which order log1 and log2 will be created (trying that with watch(1) show that the two files will swap inodes quite frequently, the more busy the system, the faster ;-)).– mosvy
25 mins ago
I'm not using QNX so I cannot give you an answer, but IMHO it would be very foolish to rely on that. Something trivial like the installer parallelizing some ops, as in foo
2>log1 | bar 2>log2 may completely defeat it, since there's no telling in which order log1 and log2 will be created (trying that with watch(1) show that the two files will swap inodes quite frequently, the more busy the system, the faster ;-)).– mosvy
25 mins ago
add a comment |
0
active
oldest
votes
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%2f538355%2fhow-does-the-sequence-of-inode-numbers-work-can-i-expect-consistency-across-ide%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f538355%2fhow-does-the-sequence-of-inode-numbers-work-can-i-expect-consistency-across-ide%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
Related: How to keep i-node consistent across separate Filesystems
– Kusalananda♦
4 hours ago
Even more related: Making bit identical ext2 filesystems
– Kusalananda♦
4 hours ago
It would not be enough to know what Unix you use, it would also be necessary to know what type of filesystem you use. I know of no common filesystem on Unix that use sequential numbering of inodes. I also don't quite know what you mean by "sequential". Do you mean sequentially stored on disk or sequentially created? Have a look at the inodes of the files in few large directories, on the systems I use, some may look sequential, but there are often big jumps. In general, inodes between devices can not be expected to refer to the same files.
– Kusalananda♦
4 hours ago
1
1) Will add to question. 2) By sequential, I mean the inode numbers for sequentially created files. For example, I did a test
echo test1>test1thenecho test2>test2, and test2's inode number was 1 higher than test1's (ie: file1's: 1234, file2's: 1235) @Kusalananda Also, I will look into the links you provided. Thank you.– Aaron
3 hours ago
I'm not using QNX so I cannot give you an answer, but IMHO it would be very foolish to rely on that. Something trivial like the installer parallelizing some ops, as in foo
2>log1 | bar 2>log2may completely defeat it, since there's no telling in which orderlog1andlog2will be created (trying that withwatch(1)show that the two files will swap inodes quite frequently, the more busy the system, the faster ;-)).– mosvy
25 mins ago