CentOS zsh: locking failed for /root/.zsh_history: read-only file system: reading anyway The 2019 Stack Overflow Developer Survey Results Are InHome 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
Potential by Assembling Charges
Understanding the implication of what "well-defined" means for the operation in quotient group
What could be the right powersource for 15 seconds lifespan disposable giant chainsaw?
Geography at the pixel level
Is "plugging out" electronic devices an American expression?
Find number from a line and get the quotient
How are circuits which use complex ICs normally simulated?
How do you say "canon" as in "official for a story universe"?
Inflated grade on resume at previous job, might former employer tell new employer?
I see my dog run
Differentiate between line ending within polygon and line passing all the way through polygon - QGIS
A poker game description that does not feel gimmicky
Flying Bloodthirsty Lampshades
Can a zener diode with a higher power dissipation be used in place of the original one in an audio amplifier?
Could JWST stay at L2 "forever"?
Dual Citizen. Exited the US on Italian passport recently
Return to UK after being refused entry years previously
The difference between dialogue marks
How is radar separation assured between primary and secondary targets?
How was Skylab's orbit inclination chosen?
If the Wish spell is used to duplicate the effect of Simulacrum, are existing duplicates destroyed?
aging parents with no investments
How to manage monthly salary
Is three citations per paragraph excessive for undergraduate research paper?
CentOS zsh: locking failed for /root/.zsh_history: read-only file system: reading anyway
The 2019 Stack Overflow Developer Survey Results Are InHome 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 16 hours ago
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 16 hours ago
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 16 hours ago
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 16 hours ago
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 16 hours ago
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 13 hours ago
techGaurdian
asked 16 hours ago
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 16 hours ago
techGaurdiantechGaurdian
1064
asked 16 hours ago
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 14 hours ago
HBruijnHBruijn
56.3k1190150
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
13 hours ago
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 14 hours ago
HBruijnHBruijn
56.3k1190150
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
13 hours ago
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 14 hours ago
HBruijnHBruijn
56.3k1190150
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
13 hours ago
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 14 hours ago
HBruijnHBruijn
56.3k1190150
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 14 hours ago
HBruijnHBruijn
56.3k1190150
answered 14 hours ago
HBruijnHBruijn
56.3k1190150
answered 14 hours ago
HBruijnHBruijn
56.3k1190150
answered 14 hours ago
HBruijnHBruijn
56.3k1190150
56.3k1190150
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
13 hours ago
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
13 hours ago
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
13 hours ago
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
13 hours ago
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
