Remount as read only is showing busy , how to remount as read only safely?
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
When trying remount , mount /path busy always.
mount -o remount,ro /path
mount: /path is busy
Is there any method to remount it as read only safely ?
What is the method to check why it is busy ?
Have tried lsof but shows nothing .
mount
asked Jun 7 at 10:53
Amruth A
787
add a comment |Â
up vote
1
down vote
favorite
When trying remount , mount /path busy always.
mount -o remount,ro /path
mount: /path is busy
Is there any method to remount it as read only safely ?
What is the method to check why it is busy ?
Have tried lsof but shows nothing .
mount
asked Jun 7 at 10:53
Amruth A
787
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
When trying remount , mount /path busy always.
mount -o remount,ro /path
mount: /path is busy
Is there any method to remount it as read only safely ?
What is the method to check why it is busy ?
Have tried lsof but shows nothing .
mount
asked Jun 7 at 10:53
Amruth A
787
When trying remount , mount /path busy always.
mount -o remount,ro /path
mount: /path is busy
Is there any method to remount it as read only safely ?
What is the method to check why it is busy ?
Have tried lsof but shows nothing .
mount
asked Jun 7 at 10:53
Amruth A
787
asked Jun 7 at 10:53
Amruth A
787
asked Jun 7 at 10:53
Amruth A
787
asked Jun 7 at 10:53
Amruth A
787
787
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
There isn't really a way to 'safely' force it read-only. Anything that did would either:
- Not really be read-only, because there would still be a file opened for write or append on the filesystem
or:
- Crash whatever application has a writable file open on that mount point.
As far as figuring out what is holding it open, try fuser -m /path. I've found it's significantly more reliable for quickly finding out what is usingg a given mount point.
answered Jun 7 at 18:56
Austin Hemmelgarn
5,049915
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
There isn't really a way to 'safely' force it read-only. Anything that did would either:
- Not really be read-only, because there would still be a file opened for write or append on the filesystem
or:
- Crash whatever application has a writable file open on that mount point.
As far as figuring out what is holding it open, try fuser -m /path. I've found it's significantly more reliable for quickly finding out what is usingg a given mount point.
answered Jun 7 at 18:56
Austin Hemmelgarn
5,049915
add a comment |Â
up vote
1
down vote
accepted
There isn't really a way to 'safely' force it read-only. Anything that did would either:
- Not really be read-only, because there would still be a file opened for write or append on the filesystem
or:
- Crash whatever application has a writable file open on that mount point.
As far as figuring out what is holding it open, try fuser -m /path. I've found it's significantly more reliable for quickly finding out what is usingg a given mount point.
answered Jun 7 at 18:56
Austin Hemmelgarn
5,049915
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
There isn't really a way to 'safely' force it read-only. Anything that did would either:
- Not really be read-only, because there would still be a file opened for write or append on the filesystem
or:
- Crash whatever application has a writable file open on that mount point.
As far as figuring out what is holding it open, try fuser -m /path. I've found it's significantly more reliable for quickly finding out what is usingg a given mount point.
answered Jun 7 at 18:56
Austin Hemmelgarn
5,049915
There isn't really a way to 'safely' force it read-only. Anything that did would either:
- Not really be read-only, because there would still be a file opened for write or append on the filesystem
or:
- Crash whatever application has a writable file open on that mount point.
As far as figuring out what is holding it open, try fuser -m /path. I've found it's significantly more reliable for quickly finding out what is usingg a given mount point.
answered Jun 7 at 18:56
Austin Hemmelgarn
5,049915
answered Jun 7 at 18:56
Austin Hemmelgarn
5,049915
answered Jun 7 at 18:56
Austin Hemmelgarn
5,049915
answered Jun 7 at 18:56
Austin Hemmelgarn
5,049915
5,049915
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f448393%2fremount-as-read-only-is-showing-busy-how-to-remount-as-read-only-safely%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
