[GH-ISSUE #2205] Summarize inspection with FUSE-T(macOS) #1119

Open
opened 2026-03-04 01:51:32 +03:00 by kerem · 2 comments
Owner

Originally created by @ggtakec on GitHub (Jul 2, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2205

Currently testing to use macos-fuse-t instead of osxfuse(macfuse) - #2198
I would like to summarize this in this issue.

Originally created by @ggtakec on GitHub (Jul 2, 2023). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2205 Currently testing to use macos-fuse-t instead of osxfuse(macfuse) - #2198 I would like to summarize this in this issue.
Author
Owner

@ggtakec commented on GitHub (Jul 2, 2023):

I'm currently testing(fuse-t: 1.0.20), but there are some things we need to check.
(Because the investigation has not been completed yet, there is a high possibility that it is not a problem in combination with fuse-t, but a problem with s3fs alone, so please be careful.)

# Owners of directories and files to be created

It seems that it will be always created by root user.

# On rare occasions, an error occurred in directory listings and some directories could not be displayed.

At this time the following error is displayed:

ls: fts_read: Input/output error

It seems that this is a symptom similar to #2182 and #2190.
I think it's likely an s3fs issue, not due to the combination with fuse-t.

# timestamp(atime/ctime/mtime) seems to behave incorrectly

I haven't been able to confirm it at all, but it may be because it is via NFS (Is there a possibility?)
We need to check logs.
The following tests are failing:

  • test_mtime_file
  • test_update_time_touch_a
  • test_update_directory_time_chown
  • test_update_directory_time_set_xattr
  • test_update_directory_time_touch_a
  • test_update_parent_directory_time
<!-- gh-comment-id:1616540729 --> @ggtakec commented on GitHub (Jul 2, 2023): I'm currently testing(fuse-t: 1.0.20), but there are some things we need to check. _(Because the investigation has not been completed yet, there is a high possibility that it is not a problem in combination with fuse-t, but a problem with s3fs alone, so please be careful.)_ #### # Owners of directories and files to be created It seems that it will be always created by root user. #### # On rare occasions, an error occurred in directory listings and some directories could not be displayed. At this time the following error is displayed: ``` ls: fts_read: Input/output error ``` It seems that this is a symptom similar to #2182 and #2190. I think it's likely an s3fs issue, not due to the combination with fuse-t. #### # timestamp(atime/ctime/mtime) seems to behave incorrectly I haven't been able to confirm it at all, but it may be because it is via NFS (Is there a possibility?) We need to check logs. The following tests are failing: - test_mtime_file - test_update_time_touch_a - test_update_directory_time_chown - test_update_directory_time_set_xattr - test_update_directory_time_touch_a - test_update_parent_directory_time
Author
Owner

@alexfs commented on GitHub (Jul 9, 2023):

test_mtime_file, test_update_time_touch_a and test_update_directory_time_touch_a are not going to work because the macos nfs server has the following bug: it's not possible to update access time separately from modified time, only together.
Other tests should work. I tested chown and xattr commands manually and it worked correctly.

<!-- gh-comment-id:1627803332 --> @alexfs commented on GitHub (Jul 9, 2023): test_mtime_file, test_update_time_touch_a and test_update_directory_time_touch_a are not going to work because the macos nfs server has the following bug: it's not possible to update access time separately from modified time, only together. Other tests should work. I tested chown and xattr commands manually and it worked correctly.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/s3fs-fuse#1119
No description provided.