-
Notifications
You must be signed in to change notification settings - Fork 21
Add timeout for nfs mount within kdumpctl & mkdumprd #124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Summary of ChangesHello @liutgnu, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces crucial timeout mechanisms for Network File System (NFS) mount operations within the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a timeout for NFS mount operations in kdumpctl and mkdumprd to prevent indefinite hangs during network instability. The changes are well-implemented and address the issue described. The updated error message in mkdumprd is also a helpful addition. I have a couple of minor suggestions to initialize variables for improved code clarity and robustness.
In kdumpctl and mkdumprd, for nfs dump target, cmd mount will be used to
mount nfs dump target to local directory. However there is no time limit
for mount, and it may take a long time for mount to finish, no matter
success or fail, when network connection is unstable.
E.g we can emulate the package loss using the following command:
$ tc qdisc add dev tun0 root handle 1: prio
$ tc qdisc add dev tun0 parent 1:3 handle 30: netem delay 2000ms 1000ms loss 80%
$ tc filter add dev tun0 protocol ip parent 1:0 prio 3 u32 match ip dst <nfs_server_ip> flowid 1:3
This will emulate 80% network package loss to <nfs_server_ip>, then we
invoke nfs mount:
$ time mount -t nfs <nfs_server_ip>:<nfs_dir> /mnt
real 354m56.200s
user 0m0.003s
sys 0m0.013s
$ mount | grep nfs
<nfs_server_ip>:<nfs_dir> on /mnt type nfs4 (...)
As we can see, though mount succeeded finally, it took near 6h to finish. The
long time waiting makes no sense and should be ended as early, so user can
check network issues and retry.
This issue also noticed in QE testing, because for beaker test tasks, if
one task doesn't finish within a specific time period, the task will be
killed and fail. We'd better set a timeout limit for nfs mount, in order
to prevent it from connecting to nfs server timelessly.
This patch will set timeout duration as 5min for kdumpctl, and 10min for
mkdumprd, as I think they are enough for normal cases as well as bail
out as early if network do encounter problems.
Signed-off-by: Tao Liu <[email protected]>
In kdumpctl and mkdumprd, for nfs dump target, cmd mount will be used to mount nfs dump target to local directory. However there is no time limit for mount, and it may take a long time for mount to finish, no matter success or fail, when network connection is unstable.
E.g we can emulate the package loss using the following command:
This will emulate 80% network package loss to <nfs_server_ip>, then we invoke nfs mount:
As we can see, though mount succeeded finally, it took near 6h to finish. The long time waiting makes no sense and should be ended as early, so user can check network issues and retry.
This issue also noticed in QE testing, because for beaker test tasks, if one task doesn't finish within a specific time period, the task will be killed and fail. We'd better set a timeout limit for nfs mount, in order to prevent it from connecting to nfs server timelessly.
This patch will set timeout duration as 5min for kdumpctl, and 10min for mkdumprd, as I think they are enough for normal cases as well as bail out as early if network do encounter problems.