Skip to content
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

os/bluestore: no need to fsync when failed to write label #20092

Merged
merged 1 commit into from Jan 29, 2018

Conversation

tangwenjun3
Copy link
Contributor

Signed-off-by: tangwenjun tang.wenjun3@zte.com.cn

@liewegas liewegas changed the title os/bluestore.cc: not need to fsync when failed to write label os/bluestore: not need to fsync when failed to write label Jan 24, 2018
@@ -4160,6 +4160,8 @@ int BlueStore::_write_bdev_label(CephContext *cct,
if (r < 0) {
derr << __func__ << " failed to write to " << path
<< ": " << cpp_strerror(r) << dendl;
VOID_TEMP_FAILURE_RETRY(::close(fd));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead, can you 'goto out', and add an out: label on the VOID_TEMP_FAILURE... line below?

@tangwenjun3 tangwenjun3 force-pushed the wip-fix-write-label branch 3 times, most recently from 257d169 to 3ebb5cc Compare January 25, 2018 01:09
@tangwenjun3 tangwenjun3 changed the title os/bluestore: not need to fsync when failed to write label os/bluestore: no need to fsync when failed to write label Jan 25, 2018
Signed-off-by: tangwenjun <tang.wenjun3@zte.com.cn>
@tangwenjun3
Copy link
Contributor Author

@liewegas fixed

@liewegas
Copy link
Member

thanks, looks good!

@tchaikov tchaikov merged commit 9c45641 into ceph:master Jan 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants