Sample Header Ad - 728x90

Unix & Linux Stack Exchange

Q&A for users of Linux, FreeBSD and other Unix-like operating systems

Latest Questions

0 votes
2 answers
106 views
Auto-mounting the 2nd internal HD
I'm editing the fstab file to automount my secondary HD and I would like to know how to setup the 'noatime' in the command line. The command I have so far is: UUID=DEVICEID /PATH ntfs-3g rw,uid=1000,gid=1000,umask=0022,fmask=0022 0 2 Where should I add the 'noatime' command in this case? Any thought...
I'm editing the fstab file to automount my secondary HD and I would like to know how to setup the 'noatime' in the command line. The command I have so far is: UUID=DEVICEID /PATH ntfs-3g rw,uid=1000,gid=1000,umask=0022,fmask=0022 0 2 Where should I add the 'noatime' command in this case? Any thoughts are appreciated.
Rival Consoles (101 rep)
Jan 16, 2022, 03:34 AM • Last activity: Jan 16, 2022, 04:33 AM
0 votes
1 answers
1427 views
`noatime` mount option's effect on `stat` access time
I have mounted ext4 partition in Ubuntu 20.04 with noatime mount option in my /etc/fstab From `stat`: Access time doesn't change when the file is opened on the editor or modified and saved, while modification time changes. Even when the file is repeatedly modified and saved, closed and saved the Acc...
I have mounted ext4 partition in Ubuntu 20.04 with noatime mount option in my /etc/fstab From stat: Access time doesn't change when the file is opened on the editor or modified and saved, while modification time changes. Even when the file is repeatedly modified and saved, closed and saved the Access time doesn't change. So, when does Access time change in noatime mounted partition? Does it ever change? Does it represent the creation time (in noatime) or when it was copied to the partition?
Porcupine (2156 rep)
Mar 20, 2021, 07:21 PM • Last activity: Mar 20, 2021, 11:34 PM
0 votes
1 answers
449 views
How to prevent `atime` in Linux from overwriting `Date created` in Windows on NTFS?
From Linux, if I alter files on an NTFS external HD so that I get some specific values for `mtime`, `atime` and `ctime` (readable with the `stat` command, and with `ctime = mtime` because one cannot change access permissions of files on NTFS from Linux - I think) and if I then connect the same exter...
From Linux, if I alter files on an NTFS external HD so that I get some specific values for mtime, atime and ctime (readable with the stat command, and with ctime = mtime because one cannot change access permissions of files on NTFS from Linux - I think) and if I then connect the same external HD on a Windows 7 system, I see that Date modified = mtime (as expected) but I also get Date created = atime. How comes atime takes the placeholder associated with the NTFS CTime timestamp, and is there a way to avoid this behavior, for example would using the noatime option on NTFS volumes be a proper solution? My goal is to be able to work from both Windows and Linux on this same external HD without mingling too much the timestamps. **Edit** After re-investigating the issue, it turns out that the problem is not present in the end. I must have been confused at the time I asked the question. I still leave the question as it has generated some comments and an answer.
The Quark (402 rep)
May 17, 2019, 05:41 PM • Last activity: May 31, 2019, 03:30 PM
0 votes
2 answers
2754 views
Setting noatime via mount options vs no atime updates (A) file attribute
From `man chattr` > When a file with the 'A' attribute set is accessed, its atime record > is not modified. This avoids a certain amount of disk I/O for laptop > systems. However when I am remounting a filesystem with the `noatime` mount option: [root@localhost ~]# mount -o remount,noatime /dev/sdb1...
From man chattr > When a file with the 'A' attribute set is accessed, its atime record > is not modified. This avoids a certain amount of disk I/O for laptop > systems. However when I am remounting a filesystem with the noatime mount option: [root@localhost ~]# mount -o remount,noatime /dev/sdb1 /newfs/ creating a file in it [root@localhost ~]# cd /newfs/ [root@localhost newfs]# touch myfile and getting its file attributes: [root@localhost newfs]# lsattr myfile -------------e-- myfile the A file attribute is not set despite the fact. Is this the expected behavior?
pkaramol (3109 rep)
Apr 22, 2019, 03:25 PM • Last activity: Apr 24, 2019, 12:15 AM
Showing page 1 of 4 total questions