From: chrysn <ch...@fs...> - 2007-08-27 21:05:20
|
>> i guess the different behaviour of ctime would also fall under this >> category (touching a new file on normal ext3 makes it ctime now, but >> 1970-01-01 on sshfs) >> > > Hmm, I'm not aware of this one. If I do the following on an sshfs > mount, I get normal results: > here is how the problem is shown: ~/mounted$ touch foo ~/mounted$ stat foo File: `foo' Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: fe01h/65025d Inode: 55 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ chrysn) Gid: ( 1000/ chrysn) Access: 2007-08-27 22:57:40.000000000 +0200 Modify: 2007-08-27 22:57:40.000000000 +0200 Change: 2007-08-27 22:57:40.000000000 +0200 ~$ touch foo ~$ stat foo File: `foo' Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: 12h/18d Inode: 62 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ chrysn) Gid: ( 100/ users) Access: 2007-08-27 22:57:37.000000000 +0200 Modify: 2007-08-27 22:57:37.000000000 +0200 Change: 1970-01-01 01:00:00.000000000 +0100 note the difference in the last lines > There's no such list, although the FAQ at > > http://fuse.sourceforge.net/wiki/index.php/SshfsFaq > > lists quite a few problematic things and respective workarounds. ok, i see it's a wiki; i'll add an entry there as soon as i know whether that other issue is a regular bug or a fundamental issue. chrysn |