What order should I restore timestamps including with debugfs?
by maybeJosiah from LinuxQuestions.org on (#6HN6F)
Okay so I know there is "touch" and "debugfs" with "set_inode_field" for setting timestamps. First can anyone check if debugfs actually can set crtime and ctime (created at and changed at)?
crtime:
https://zzzcode.ai/answer-question?i...b-909627aff1d8
ctime (replace ctime with crtime for crtime):
https://zzzcode.ai/answer-question?i...5-3422a295e7c7
Accessed at time:
touch -a -d access_time file_path
Modified time:
touch -m -d access_time file_path
With those commands, maybe just second zzzcode thing with stat for inode, what order should I restore to get all values for timestamps set? Also, does debugfs actually set created at time and changed at time? NOTE: DEBUGFS IS NOT FOR "REGULAR USE", BE CAREFUL. I am on an Ubuntu desktop 22.04.3 with Ubuntu Pro Lenovo Thinkpad T460. All as per one might be maybe or might not be maybe, maybe or maybe not, maybe.
crtime:
https://zzzcode.ai/answer-question?i...b-909627aff1d8
ctime (replace ctime with crtime for crtime):
https://zzzcode.ai/answer-question?i...5-3422a295e7c7
Accessed at time:
touch -a -d access_time file_path
Modified time:
touch -m -d access_time file_path
With those commands, maybe just second zzzcode thing with stat for inode, what order should I restore to get all values for timestamps set? Also, does debugfs actually set created at time and changed at time? NOTE: DEBUGFS IS NOT FOR "REGULAR USE", BE CAREFUL. I am on an Ubuntu desktop 22.04.3 with Ubuntu Pro Lenovo Thinkpad T460. All as per one might be maybe or might not be maybe, maybe or maybe not, maybe.