What is the meaning of below picture. I ran fsck -c / then I got below output The 2019 Stack Overflow Developer Survey Results Are InShould I be worried? Segfaults reported in syslog when merging LVM snapshot (reverting the original back to the snapshot)Valley View “Black Screen of Death”Which process scheduler is my linux system using?Problem with grep on multiple files and not getting desired outputSSH Connection Timed OutHow to grep response to figure out how many calls got timed out?How can I have a pingable IP but the wireess interface is unassociated?rm -rf directory with 0 size and blocksNeed Intel Xeon E3-1200 drivers for Linux Mint 18Tail with case statement is not working properly
Button changing its text & action. Good or terrible?
Is one supposed to eat the zero'ah (shank bone) from the Seder plate?
Will it cause any balance problems to have PCs level up and gain the benefits of a long rest mid-fight?
Did the UK government pay "millions and millions of dollars" to try to snag Julian Assange?
Did Scotland spend $250,000 for the slogan "Welcome to Scotland"?
What information about me do stores get via my credit card?
Flight paths in orbit around Ceres?
Is an up-to-date browser secure on an out-of-date OS?
Can there be female White Walkers?
Why can't devices on different VLANs, but on the same subnet, communicate?
How much of the clove should I use when using big garlic heads?
Kerning for subscripts of sigma?
How to obtain a position of last non-zero element
How did passengers keep warm on sail ships?
If I can cast sorceries at instant speed, can I use sorcery-speed activated abilities at instant speed?
How can I add encounters in the Lost Mine of Phandelver campaign without giving PCs too much XP?
What is the most efficient way to store a numeric range?
What does Linus Torvalds mean when he says that Git "never ever" tracks a file?
Getting crown tickets for Statue of Liberty
I am an eight letter word. What am I?
Geography at the pixel level
How to charge AirPods to keep battery healthy?
Why didn't the Event Horizon Telescope team mention Sagittarius A*?
Is bread bad for ducks?
What is the meaning of below picture. I ran fsck -c / then I got below output
The 2019 Stack Overflow Developer Survey Results Are InShould I be worried? Segfaults reported in syslog when merging LVM snapshot (reverting the original back to the snapshot)Valley View “Black Screen of Death”Which process scheduler is my linux system using?Problem with grep on multiple files and not getting desired outputSSH Connection Timed OutHow to grep response to figure out how many calls got timed out?How can I have a pingable IP but the wireess interface is unassociated?rm -rf directory with 0 size and blocksNeed Intel Xeon E3-1200 drivers for Linux Mint 18Tail with case statement is not working properly
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
- I unmounted "/" then I ran fsck -c after that I got below out put. please tell me what it is exact meaning.
- And also tell me if I get below output it means will my problem resolved? Please provide a step by step answer dont confuse me.
linux
asked 2 days ago
GangasagarGangasagar
11
add a comment |
- I unmounted "/" then I ran fsck -c after that I got below out put. please tell me what it is exact meaning.
- And also tell me if I get below output it means will my problem resolved? Please provide a step by step answer dont confuse me.
linux
asked 2 days ago
GangasagarGangasagar
11
4
Welcome to U/L. Please do not post images. Please remove the image and replace it with the raw text.
– Sparhawk
2 days ago
Unmounting/would make/sbin/fscknot accessible, so I think you either failed to unmount/or actually did something different, like switched it to read-only mode.
– telcoM
yesterday
add a comment |
- I unmounted "/" then I ran fsck -c after that I got below out put. please tell me what it is exact meaning.
- And also tell me if I get below output it means will my problem resolved? Please provide a step by step answer dont confuse me.
linux
asked 2 days ago
GangasagarGangasagar
11
- I unmounted "/" then I ran fsck -c after that I got below out put. please tell me what it is exact meaning.
- And also tell me if I get below output it means will my problem resolved? Please provide a step by step answer dont confuse me.
linux
linux
asked 2 days ago
GangasagarGangasagar
11
asked 2 days ago
GangasagarGangasagar
11
asked 2 days ago
GangasagarGangasagar
11
asked 2 days ago
GangasagarGangasagar
11
asked 2 days ago
GangasagarGangasagar
11
11
4
Welcome to U/L. Please do not post images. Please remove the image and replace it with the raw text.
– Sparhawk
2 days ago
Unmounting/would make/sbin/fscknot accessible, so I think you either failed to unmount/or actually did something different, like switched it to read-only mode.
– telcoM
yesterday
add a comment |
4
Welcome to U/L. Please do not post images. Please remove the image and replace it with the raw text.
– Sparhawk
2 days ago
Unmounting/would make/sbin/fscknot accessible, so I think you either failed to unmount/or actually did something different, like switched it to read-only mode.
– telcoM
yesterday
4
4
Welcome to U/L. Please do not post images. Please remove the image and replace it with the raw text.
– Sparhawk
2 days ago
Welcome to U/L. Please do not post images. Please remove the image and replace it with the raw text.
– Sparhawk
2 days ago
Unmounting
/ would make /sbin/fsck not accessible, so I think you either failed to unmount / or actually did something different, like switched it to read-only mode.– telcoM
yesterday
Unmounting
/ would make /sbin/fsck not accessible, so I think you either failed to unmount / or actually did something different, like switched it to read-only mode.– telcoM
yesterday
add a comment |
1 Answer
1
active
oldest
votes
The fsck command did read through the entire logical volume to look for bad blocks, and then made some change to the list of bad blocks within the filesystem. Then it ran the standard 5 filesystem consistency check passes and found nothing wrong.
As this is your current root filesystem, it cannot really be unmounted, only remounted in read-only mode. That means, even if the filesystem is in read-only mode, any data read from the filesystem will still be cached in the system RAM. So it is possible that old data (in this case, specifically the old version of the bad blocks list) is still in RAM cache and might be used and eventually written back to the disk if the filesystem is switched to read/write mode without rebooting. Because of this, it is important to reboot the system after running fsck on your root filesystem if fsck did have to make any changes to the filesystem, no matter how small. And apart fromt the bad block information update, it appears fsck did not need to do anything else.
You should now reboot, then run dumpe2fs -b /dev/mapper/RootVolGroup00-lv_root to view the current list of bad blocks detected at the filesystem level. If it only displays the version number of the dumpe2fs command, there were no bad blocks detected.
Note: if there are any bad blocks detected at the filesystem level, that very likely means the disk's internal firmware-based bad block replacement mechanism is already been overwhelmed by the number of bad blocks on the disk. In that case I would immediately make sure my backups are up to date, and would seriously consider replacing the disk as a precaution.
You might want to use smartctl -HA -f brief /dev/sda or similar to get more information about the health of the disk.
answered yesterday
telcoMtelcoM
20.8k12452
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
);
);
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%2funix.stackexchange.com%2fquestions%2f511561%2fwhat-is-the-meaning-of-below-picture-i-ran-fsck-c-then-i-got-below-output%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 fsck command did read through the entire logical volume to look for bad blocks, and then made some change to the list of bad blocks within the filesystem. Then it ran the standard 5 filesystem consistency check passes and found nothing wrong.
As this is your current root filesystem, it cannot really be unmounted, only remounted in read-only mode. That means, even if the filesystem is in read-only mode, any data read from the filesystem will still be cached in the system RAM. So it is possible that old data (in this case, specifically the old version of the bad blocks list) is still in RAM cache and might be used and eventually written back to the disk if the filesystem is switched to read/write mode without rebooting. Because of this, it is important to reboot the system after running fsck on your root filesystem if fsck did have to make any changes to the filesystem, no matter how small. And apart fromt the bad block information update, it appears fsck did not need to do anything else.
You should now reboot, then run dumpe2fs -b /dev/mapper/RootVolGroup00-lv_root to view the current list of bad blocks detected at the filesystem level. If it only displays the version number of the dumpe2fs command, there were no bad blocks detected.
Note: if there are any bad blocks detected at the filesystem level, that very likely means the disk's internal firmware-based bad block replacement mechanism is already been overwhelmed by the number of bad blocks on the disk. In that case I would immediately make sure my backups are up to date, and would seriously consider replacing the disk as a precaution.
You might want to use smartctl -HA -f brief /dev/sda or similar to get more information about the health of the disk.
answered yesterday
telcoMtelcoM
20.8k12452
add a comment |
The fsck command did read through the entire logical volume to look for bad blocks, and then made some change to the list of bad blocks within the filesystem. Then it ran the standard 5 filesystem consistency check passes and found nothing wrong.
As this is your current root filesystem, it cannot really be unmounted, only remounted in read-only mode. That means, even if the filesystem is in read-only mode, any data read from the filesystem will still be cached in the system RAM. So it is possible that old data (in this case, specifically the old version of the bad blocks list) is still in RAM cache and might be used and eventually written back to the disk if the filesystem is switched to read/write mode without rebooting. Because of this, it is important to reboot the system after running fsck on your root filesystem if fsck did have to make any changes to the filesystem, no matter how small. And apart fromt the bad block information update, it appears fsck did not need to do anything else.
You should now reboot, then run dumpe2fs -b /dev/mapper/RootVolGroup00-lv_root to view the current list of bad blocks detected at the filesystem level. If it only displays the version number of the dumpe2fs command, there were no bad blocks detected.
Note: if there are any bad blocks detected at the filesystem level, that very likely means the disk's internal firmware-based bad block replacement mechanism is already been overwhelmed by the number of bad blocks on the disk. In that case I would immediately make sure my backups are up to date, and would seriously consider replacing the disk as a precaution.
You might want to use smartctl -HA -f brief /dev/sda or similar to get more information about the health of the disk.
answered yesterday
telcoMtelcoM
20.8k12452
add a comment |
The fsck command did read through the entire logical volume to look for bad blocks, and then made some change to the list of bad blocks within the filesystem. Then it ran the standard 5 filesystem consistency check passes and found nothing wrong.
As this is your current root filesystem, it cannot really be unmounted, only remounted in read-only mode. That means, even if the filesystem is in read-only mode, any data read from the filesystem will still be cached in the system RAM. So it is possible that old data (in this case, specifically the old version of the bad blocks list) is still in RAM cache and might be used and eventually written back to the disk if the filesystem is switched to read/write mode without rebooting. Because of this, it is important to reboot the system after running fsck on your root filesystem if fsck did have to make any changes to the filesystem, no matter how small. And apart fromt the bad block information update, it appears fsck did not need to do anything else.
You should now reboot, then run dumpe2fs -b /dev/mapper/RootVolGroup00-lv_root to view the current list of bad blocks detected at the filesystem level. If it only displays the version number of the dumpe2fs command, there were no bad blocks detected.
Note: if there are any bad blocks detected at the filesystem level, that very likely means the disk's internal firmware-based bad block replacement mechanism is already been overwhelmed by the number of bad blocks on the disk. In that case I would immediately make sure my backups are up to date, and would seriously consider replacing the disk as a precaution.
You might want to use smartctl -HA -f brief /dev/sda or similar to get more information about the health of the disk.
answered yesterday
telcoMtelcoM
20.8k12452
The fsck command did read through the entire logical volume to look for bad blocks, and then made some change to the list of bad blocks within the filesystem. Then it ran the standard 5 filesystem consistency check passes and found nothing wrong.
As this is your current root filesystem, it cannot really be unmounted, only remounted in read-only mode. That means, even if the filesystem is in read-only mode, any data read from the filesystem will still be cached in the system RAM. So it is possible that old data (in this case, specifically the old version of the bad blocks list) is still in RAM cache and might be used and eventually written back to the disk if the filesystem is switched to read/write mode without rebooting. Because of this, it is important to reboot the system after running fsck on your root filesystem if fsck did have to make any changes to the filesystem, no matter how small. And apart fromt the bad block information update, it appears fsck did not need to do anything else.
You should now reboot, then run dumpe2fs -b /dev/mapper/RootVolGroup00-lv_root to view the current list of bad blocks detected at the filesystem level. If it only displays the version number of the dumpe2fs command, there were no bad blocks detected.
Note: if there are any bad blocks detected at the filesystem level, that very likely means the disk's internal firmware-based bad block replacement mechanism is already been overwhelmed by the number of bad blocks on the disk. In that case I would immediately make sure my backups are up to date, and would seriously consider replacing the disk as a precaution.
You might want to use smartctl -HA -f brief /dev/sda or similar to get more information about the health of the disk.
answered yesterday
telcoMtelcoM
20.8k12452
answered yesterday
telcoMtelcoM
20.8k12452
answered yesterday
telcoMtelcoM
20.8k12452
answered yesterday
telcoMtelcoM
20.8k12452
20.8k12452
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f511561%2fwhat-is-the-meaning-of-below-picture-i-ran-fsck-c-then-i-got-below-output%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
-linux
4
Welcome to U/L. Please do not post images. Please remove the image and replace it with the raw text.
– Sparhawk
2 days ago
Unmounting
/would make/sbin/fscknot accessible, so I think you either failed to unmount/or actually did something different, like switched it to read-only mode.– telcoM
yesterday