Skip to content

Amazon FSx for openZFS mount connection time out

0

I have created ubuntu EC2 instance on North Virginia region with custom VPC. I have created file system with Amazon FSx for open ZFS as same subnets and same AZ. I have created two security groups, One for EC2 instance as EFS Target Security group another one for file system as EFS Mount Security group. I added inbound rules SSH and outbound rules NFS Port with destination as Filesystem security group. I added inbound rules NFS Port with source as EC2 instance security group and File system Security group. Both EC2 instance and File system placed on same subnet and same Availability zone. Finally, i tried to mount this file system on my EC2 instance. However, This mount point not connected. Its throwing connection time out error on ubuntu terminal.

$ sudo mount -t nfs -o nfsvers=4.2 file-system-endpoint:/fsx/ /home/ubuntu/.wine/drive_c/eagfs/

Error: mount.nfs: Connection timed out

Can any one help me to sort out from this issues?

Note: I have asked this same questions on stackoverflow too, But no answer on this thread. I shared link.

https://stackoverflow.com/questions/70388601/amazon-fsx-for-openzfs-mount-connection-time-out

3 Answers
0

Hi,

From looking at your stackoverflow post, I suspect the issue might be that you don't have the File System security group configured properly. Take a look at the link below for additional inbound rules to add:

https://docs.aws.amazon.com/fsx/latest/OpenZFSGuide/limit-access-security-groups.html

AWS

answered 5 years ago

  • Thanks Tom, I have just followed the link you were shared to create security group for Open ZFS file system. I added inbound rules custom TCP and UDP with port numbers : 111, 2049, 20001-20003 and added outbound rules to all. However, still I'm facing mount timed out error.

  • Any update on this? I have tried multiple time with Security group (Any where) for both EC2 and ZFS security group. However, no luck. Can any please help on this?

  • Hi Latchu, Happy new year! Have you tried running Reachability Analyzer, it can look at the path between your instance and the OpenZFS ENI, to determine if it is accessible based on your configuration. More details here: https://docs.aws.amazon.com/vpc/latest/reachability/getting-started.html

  • HI Tom, Yes i have checked with Reachability Analyzer for both TCP and RDP. Both are accessible. Where I'm wrong? I don't why connection timed-out even all ports are opened to anywhere in both EC2 and OpenZFS security group.

0

I am facing the same problem. I have the same VPC, same Availability Zone, and the communication within the VPC is fully permitted (0.0.0.0.0/0 all communication) by ACL. I applied a Security Group with full permission (0.0.0.0.0/0 all communication) to the EIP attached to FSx OpenZFS just to be sure, but I cannot communicate with both ping and nfs(2049).

answered 4 years ago

0

[For future reference] When configuring your network and security settings, did you leave the “select route tables” option set to default, or did you include all the route tables from the dropdown menu? That’s likely the issue.

It’s possible that the Route Table associated with your FileSystem is not the same as the one used by your EC2 instance, which could be preventing you from successfully mounting it.

To check:

Go to the FileSystems section and review the Network & Security tab to identify the associated Route Table. Next, navigate to Instances, select your EC2 instance, and check its Subnet ID in the Networking tab (click on the Subnet ID link). This will show you the Route Table associated with the instance’s subnet. If the Route Tables don’t match, it’s likely that the instance is not properly configured to access the FileSystem (you can manually update the route table and retry).

Hope that helps.

AWS
EXPERT

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.