CentOS zsh: locking failed for /root/.zsh_history: read-only file system: reading anyway Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!Home directory mounted read only file systemCannot mount cdrom in Linux due to “I/O error”Remount read-only device as read-write on xen guestApache serves garbage contentAlmost All Xenserver Logical Volumes Disappeared - Recovery?XenServer 6.2: how to use a partition on install disk as SR?Cannot mount - busted superblock?Unexpected behaviour from dfQuestions regarding PostgreSQL virtualizationRe-allocate space from one Volume Group to another Volume Group - Linux CentOs
Using "nakedly" instead of "with nothing on"
What would be Julian Assange's expected punishment, on the current English criminal law?
I'm having difficulty getting my players to do stuff in a sandbox campaign
If A makes B more likely then B makes A more likely"
How to politely respond to generic emails requesting a PhD/job in my lab? Without wasting too much time
Determine whether f is a function, an injection, a surjection
Strange behaviour of Check
Can I throw a longsword at someone?
What's the difference between (size_t)-1 and ~0?
Limit for e and 1/e
What is the electric potential inside a point charge?
Problem when applying foreach loop
Area of a 2D convex hull
Need a suitable toxic chemical for a murder plot in my novel
Why is there no army of Iron-Mans in the MCU?
Replacing HDD with SSD; what about non-APFS/APFS?
When is phishing education going too far?
How is simplicity better than precision and clarity in prose?
How should I respond to a player wanting to catch a sword between their hands?
Geometric mean and geometric standard deviation
Why is "Captain Marvel" translated as male in Portugal?
What do you call a plan that's an alternative plan in case your initial plan fails?
How to say that you spent the night with someone, you were only sleeping and nothing else?
What did Darwin mean by 'squib' here?
CentOS zsh: locking failed for /root/.zsh_history: read-only file system: reading anyway
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Home directory mounted read only file systemCannot mount cdrom in Linux due to “I/O error”Remount read-only device as read-write on xen guestApache serves garbage contentAlmost All Xenserver Logical Volumes Disappeared - Recovery?XenServer 6.2: how to use a partition on install disk as SR?Cannot mount - busted superblock?Unexpected behaviour from dfQuestions regarding PostgreSQL virtualizationRe-allocate space from one Volume Group to another Volume Group - Linux CentOs
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I am working on CentOS 7 Xen server with 100 GB memory. I have a master server with 1 TB hard disk space and 2 slave server
I increased disk space from 100 to 155 GB directly for /xen/vm4/abctest.img for virtual system /dev/xvda1
But now I get error
zsh: locking failed for /root/.zsh_history: read-only file system: reading anyway
Update
Using @HBruijn solution I tried mount -o remount,rw / but get error
mount: cannot remount /dev/xvda1 read-write, is write-protected
Appreciate any help.
centos7 mount xenserver virtualmin
asked Apr 9 at 19:03
techGaurdiantechGaurdian
1064
New contributor
techGaurdian is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I am working on CentOS 7 Xen server with 100 GB memory. I have a master server with 1 TB hard disk space and 2 slave server
I increased disk space from 100 to 155 GB directly for /xen/vm4/abctest.img for virtual system /dev/xvda1
But now I get error
zsh: locking failed for /root/.zsh_history: read-only file system: reading anyway
Update
Using @HBruijn solution I tried mount -o remount,rw / but get error
mount: cannot remount /dev/xvda1 read-write, is write-protected
Appreciate any help.
centos7 mount xenserver virtualmin
asked Apr 9 at 19:03
techGaurdiantechGaurdian
1064
New contributor
techGaurdian is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I am working on CentOS 7 Xen server with 100 GB memory. I have a master server with 1 TB hard disk space and 2 slave server
I increased disk space from 100 to 155 GB directly for /xen/vm4/abctest.img for virtual system /dev/xvda1
But now I get error
zsh: locking failed for /root/.zsh_history: read-only file system: reading anyway
Update
Using @HBruijn solution I tried mount -o remount,rw / but get error
mount: cannot remount /dev/xvda1 read-write, is write-protected
Appreciate any help.
centos7 mount xenserver virtualmin
asked Apr 9 at 19:03
techGaurdiantechGaurdian
1064
New contributor
techGaurdian is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I am working on CentOS 7 Xen server with 100 GB memory. I have a master server with 1 TB hard disk space and 2 slave server
I increased disk space from 100 to 155 GB directly for /xen/vm4/abctest.img for virtual system /dev/xvda1
But now I get error
zsh: locking failed for /root/.zsh_history: read-only file system: reading anyway
Update
Using @HBruijn solution I tried mount -o remount,rw / but get error
mount: cannot remount /dev/xvda1 read-write, is write-protected
Appreciate any help.
centos7 mount xenserver virtualmin
centos7 mount xenserver virtualmin
asked Apr 9 at 19:03
techGaurdiantechGaurdian
1064
New contributor
techGaurdian is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 9 at 19:03
techGaurdiantechGaurdian
1064
New contributor
techGaurdian is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Apr 9 at 22:10
techGaurdian
asked Apr 9 at 19:03
techGaurdiantechGaurdian
1064
New contributor
techGaurdian is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 9 at 19:03
techGaurdiantechGaurdian
1064
asked Apr 9 at 19:03
techGaurdiantechGaurdian
1064
1064
New contributor
techGaurdian is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
techGaurdian is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
techGaurdian is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The error
zsh: locking failed for /root/.zsh_history: read-only file system
seems to indicate that your system is now read-only.
The default behaviour for most Linux file systems is to safeguard your data. When the kernel detects an error in the storage subsystem it will make the filesystem read-only to prevent (further) data corruption.
You can tune this somewhat with the mount option errors=remount-ro which are documented in the system manual (man mount).
When your root file-system encounters such an error, most of the time the error won't be recorded in your log-files, as they will now be read-only too. Fortunately since it is a kernel action the original error message is recorded in memory first, in the kernel ring buffer. Unless already flushed from memory you can display the contents of the ring buffer with the dmesg command.
Resizing the storage is a likely cause though
Depending on the error messages, you could decide it is still safe to use your file-system and attempt to return it to a read-write condition with mount -o remount,rw /
answered Apr 9 at 21:02
HBruijnHBruijn
56.4k1190150
Thank you for the help. I tried with mount -o remount,rw / command but get error mount: cannot remount /dev/xvda1 read-write, is write-protected Also I get zsh: corrupt history file /root/.zsh_history when I login to server with read only file system. I have updated my question. Please is there any other way to change readonly mode. Can I reduce the hard disk drive? will that help?
– techGaurdian
Apr 9 at 21:25
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
techGaurdian is a new contributor. Be nice, and check out our Code of Conduct.
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962292%2fcentos-zsh-locking-failed-for-root-zsh-history-read-only-file-system-readin%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The error
zsh: locking failed for /root/.zsh_history: read-only file system
seems to indicate that your system is now read-only.
The default behaviour for most Linux file systems is to safeguard your data. When the kernel detects an error in the storage subsystem it will make the filesystem read-only to prevent (further) data corruption.
You can tune this somewhat with the mount option errors=remount-ro which are documented in the system manual (man mount).
When your root file-system encounters such an error, most of the time the error won't be recorded in your log-files, as they will now be read-only too. Fortunately since it is a kernel action the original error message is recorded in memory first, in the kernel ring buffer. Unless already flushed from memory you can display the contents of the ring buffer with the dmesg command.
Resizing the storage is a likely cause though
Depending on the error messages, you could decide it is still safe to use your file-system and attempt to return it to a read-write condition with mount -o remount,rw /
answered Apr 9 at 21:02
HBruijnHBruijn
56.4k1190150
Thank you for the help. I tried with mount -o remount,rw / command but get error mount: cannot remount /dev/xvda1 read-write, is write-protected Also I get zsh: corrupt history file /root/.zsh_history when I login to server with read only file system. I have updated my question. Please is there any other way to change readonly mode. Can I reduce the hard disk drive? will that help?
– techGaurdian
Apr 9 at 21:25
add a comment |
The error
zsh: locking failed for /root/.zsh_history: read-only file system
seems to indicate that your system is now read-only.
The default behaviour for most Linux file systems is to safeguard your data. When the kernel detects an error in the storage subsystem it will make the filesystem read-only to prevent (further) data corruption.
You can tune this somewhat with the mount option errors=remount-ro which are documented in the system manual (man mount).
When your root file-system encounters such an error, most of the time the error won't be recorded in your log-files, as they will now be read-only too. Fortunately since it is a kernel action the original error message is recorded in memory first, in the kernel ring buffer. Unless already flushed from memory you can display the contents of the ring buffer with the dmesg command.
Resizing the storage is a likely cause though
Depending on the error messages, you could decide it is still safe to use your file-system and attempt to return it to a read-write condition with mount -o remount,rw /
answered Apr 9 at 21:02
HBruijnHBruijn
56.4k1190150
Thank you for the help. I tried with mount -o remount,rw / command but get error mount: cannot remount /dev/xvda1 read-write, is write-protected Also I get zsh: corrupt history file /root/.zsh_history when I login to server with read only file system. I have updated my question. Please is there any other way to change readonly mode. Can I reduce the hard disk drive? will that help?
– techGaurdian
Apr 9 at 21:25
add a comment |
The error
zsh: locking failed for /root/.zsh_history: read-only file system
seems to indicate that your system is now read-only.
The default behaviour for most Linux file systems is to safeguard your data. When the kernel detects an error in the storage subsystem it will make the filesystem read-only to prevent (further) data corruption.
You can tune this somewhat with the mount option errors=remount-ro which are documented in the system manual (man mount).
When your root file-system encounters such an error, most of the time the error won't be recorded in your log-files, as they will now be read-only too. Fortunately since it is a kernel action the original error message is recorded in memory first, in the kernel ring buffer. Unless already flushed from memory you can display the contents of the ring buffer with the dmesg command.
Resizing the storage is a likely cause though
Depending on the error messages, you could decide it is still safe to use your file-system and attempt to return it to a read-write condition with mount -o remount,rw /
answered Apr 9 at 21:02
HBruijnHBruijn
56.4k1190150
The error
zsh: locking failed for /root/.zsh_history: read-only file system
seems to indicate that your system is now read-only.
The default behaviour for most Linux file systems is to safeguard your data. When the kernel detects an error in the storage subsystem it will make the filesystem read-only to prevent (further) data corruption.
You can tune this somewhat with the mount option errors=remount-ro which are documented in the system manual (man mount).
When your root file-system encounters such an error, most of the time the error won't be recorded in your log-files, as they will now be read-only too. Fortunately since it is a kernel action the original error message is recorded in memory first, in the kernel ring buffer. Unless already flushed from memory you can display the contents of the ring buffer with the dmesg command.
Resizing the storage is a likely cause though
Depending on the error messages, you could decide it is still safe to use your file-system and attempt to return it to a read-write condition with mount -o remount,rw /
answered Apr 9 at 21:02
HBruijnHBruijn
56.4k1190150
answered Apr 9 at 21:02
HBruijnHBruijn
56.4k1190150
answered Apr 9 at 21:02
HBruijnHBruijn
56.4k1190150
answered Apr 9 at 21:02
HBruijnHBruijn
56.4k1190150
56.4k1190150
Thank you for the help. I tried with mount -o remount,rw / command but get error mount: cannot remount /dev/xvda1 read-write, is write-protected Also I get zsh: corrupt history file /root/.zsh_history when I login to server with read only file system. I have updated my question. Please is there any other way to change readonly mode. Can I reduce the hard disk drive? will that help?
– techGaurdian
Apr 9 at 21:25
add a comment |
Thank you for the help. I tried with mount -o remount,rw / command but get error mount: cannot remount /dev/xvda1 read-write, is write-protected Also I get zsh: corrupt history file /root/.zsh_history when I login to server with read only file system. I have updated my question. Please is there any other way to change readonly mode. Can I reduce the hard disk drive? will that help?
– techGaurdian
Apr 9 at 21:25
Thank you for the help. I tried with mount -o remount,rw / command but get error mount: cannot remount /dev/xvda1 read-write, is write-protected Also I get zsh: corrupt history file /root/.zsh_history when I login to server with read only file system. I have updated my question. Please is there any other way to change readonly mode. Can I reduce the hard disk drive? will that help?
– techGaurdian
Apr 9 at 21:25
Thank you for the help. I tried with mount -o remount,rw / command but get error mount: cannot remount /dev/xvda1 read-write, is write-protected Also I get zsh: corrupt history file /root/.zsh_history when I login to server with read only file system. I have updated my question. Please is there any other way to change readonly mode. Can I reduce the hard disk drive? will that help?
– techGaurdian
Apr 9 at 21:25
add a comment |
techGaurdian is a new contributor. Be nice, and check out our Code of Conduct.
techGaurdian is a new contributor. Be nice, and check out our Code of Conduct.
techGaurdian is a new contributor. Be nice, and check out our Code of Conduct.
techGaurdian is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962292%2fcentos-zsh-locking-failed-for-root-zsh-history-read-only-file-system-readin%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
