[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [HS] derniere date d'acces à un point de montage



Le 30/12/2013 13:36, juke@free.fr a écrit :
Bonjour

Auriez vous une methode pour recuperer la dernière date d'acces à un point de
montage, autre que de parcours les atime de tout les fichiers le constituant ?

Merci de votre aide.

Julien.

Si par chance ton filesystem est ext[234], tu as les infos avec :
Last mount time ci dessous :

$ sudo tune2fs /dev/sda5 -l

tune2fs 1.42.5 (29-Jul-2012)
Filesystem volume name:   boot
Last mounted on:          /boot
Filesystem UUID:          f0e2856b-90e6-4721-b9e0-1c4236e6b7cb
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              24096
Block count:              96256
Reserved block count:     4812
Free blocks:              34984
Free inodes:              23825
First block:              1
Block size:               1024
Fragment size:            1024
Reserved GDT blocks:      256
Blocks per group:         8192
Fragments per group:      8192
Inodes per group:         2008
Inode blocks per group:   251
Flex block group size:    16
Filesystem created:       Fri Mar 29 12:18:20 2013
Last mount time:          Mon Dec 30 14:15:00 2013
Last write time:          Mon Dec 30 14:15:00 2013
Mount count:              93
Maximum mount count:      -1
Last checked:             Fri Mar 29 12:18:20 2013
Check interval:           0 (<none>)
Lifetime writes:          1274 MB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      4f63c0e1-b0a1-48e2-8d82-c19349fd9138
Journal backup:           inode blocks


Reply to: