Attempting to create a file in the files directory caused a crash.
Rebooting after a plain fsck after the crash came up with error
messages
savecore 982 - - reboot after panic: ufs_dirbad: /: bad dir ino
20008348 at offset 1024: mangled entry savecore 982 - - writing core
to /var/crash/vmcore.1 Sep 14 05:30:14 top savecore[982]: reboot
after panic: ufs_dirbad: /: bad dir ino 20008348 at offset 1024:
mangled entry Writing crash summary to /var/crash/core.txt.1
vmcore.1 is a 1052684288 byte file I will not reproduce here.
Is there anything particular to look for in the 176587-byte
core.txt.1 ? Is there any particular fsck option that would make
things work again?
Am Mittwoch, 14. September 2022, um 06:21:05 Uhr schrieb Louis Epstein:
Attempting to create a file in the files directory caused a crash.
Rebooting after a plain fsck after the crash came up with error
messages
savecore 982 - - reboot after panic: ufs_dirbad: /: bad dir ino
20008348 at offset 1024: mangled entry savecore 982 - - writing core
to /var/crash/vmcore.1 Sep 14 05:30:14 top savecore[982]: reboot
after panic: ufs_dirbad: /: bad dir ino 20008348 at offset 1024:
mangled entry Writing crash summary to /var/crash/core.txt.1
vmcore.1 is a 1052684288 byte file I will not reproduce here.
Is there anything particular to look for in the 176587-byte
core.txt.1 ? Is there any particular fsck option that would make
things work again?
If you run fsck, does it ask you to delete these entries?
Rebooting and saying fsck at the first prompt
gets a host of error messages with a "no" response
automatically filled in for all of them.
Am Mittwoch, 14. September 2022, um 08:34:28 Uhr schrieb Louis Epstein:
Rebooting and saying fsck at the first prompt
gets a host of error messages with a "no" response
automatically filled in for all of them.
Can you answer them with "yes"?
As I said they were automatically filled in,
probably tied to my being in / (I am familiar
with unmounting any OTHER partition when doing
fsck but how can I unmount the / when the OS is
there?...since the system isn't responding to
a crash how do I get into a different mode?)
Am Mittwoch, 14. September 2022, um 14:51:41 Uhr schrieb Louis Epstein:
As I said they were automatically filled in, probably tied to my being
in / (I am familiar with unmounting any OTHER partition when doing fsck
but how can I unmount the / when the OS is there?...since the system
isn't responding to a crash how do I get into a different mode?)
You cant do fsck with repairs on a mounted file system. You need to boot
a live system (any distribution you like, e.g. Ubuntu) and run fsck
there. Then you should be able to change the contents on the file system
that is broken.
On Wed, 14 Sep 2022 17:40:58 +0200, Marco Moock wrote:
Am Mittwoch, 14. September 2022, um 14:51:41 Uhr schrieb Louis Epstein:
As I said they were automatically filled in, probably tied to my being
in / (I am familiar with unmounting any OTHER partition when doing fsck
but how can I unmount the / when the OS is there?...since the system
isn't responding to a crash how do I get into a different mode?)
You cant do fsck with repairs on a mounted file system. You need to boot
a live system (any distribution you like, e.g. Ubuntu) and run fsck
there. Then you should be able to change the contents on the file system
that is broken.
You can if it's mounted read only. At least, that's how you fix the root
file system.
Bob Eager <news0009@eager.cx> wrote:
On Wed, 14 Sep 2022 17:40:58 +0200, Marco Moock wrote:
Am Mittwoch, 14. September 2022, um 14:51:41 Uhr schrieb Louis Epstein:
As I said they were automatically filled in, probably tied to my being >>>> in / (I am familiar with unmounting any OTHER partition when doing fsck >>>> but how can I unmount the / when the OS is there?...since the system
isn't responding to a crash how do I get into a different mode?)
You cant do fsck with repairs on a mounted file system. You need to boot >>> a live system (any distribution you like, e.g. Ubuntu) and run fsck
there. Then you should be able to change the contents on the file system >>> that is broken.
You can if it's mounted read only. At least, that's how you fix the root
file system.
(problem now fixed)
Louis Epstein <le@top.put.com> wrote in <tftd65$3es$1@reader2.panix.com>:
Bob Eager <news0009@eager.cx> wrote:
On Wed, 14 Sep 2022 17:40:58 +0200, Marco Moock wrote:
Am Mittwoch, 14. September 2022, um 14:51:41 Uhr schrieb Louis Epstein: >>>>
As I said they were automatically filled in, probably tied to my being >>>>> in / (I am familiar with unmounting any OTHER partition when doing fsck >>>>> but how can I unmount the / when the OS is there?...since the system >>>>> isn't responding to a crash how do I get into a different mode?)
You cant do fsck with repairs on a mounted file system. You need to boot >>>> a live system (any distribution you like, e.g. Ubuntu) and run fsck
there. Then you should be able to change the contents on the file system >>>> that is broken.
You can if it's mounted read only. At least, that's how you fix the root >>> file system.
(problem now fixed)
How?
mikea@mikea.ath.cx wrote:
Louis Epstein <le@top.put.com> wrote in <tftd65$3es$1@reader2.panix.com>:
Bob Eager <news0009@eager.cx> wrote:
On Wed, 14 Sep 2022 17:40:58 +0200, Marco Moock wrote:
Am Mittwoch, 14. September 2022, um 14:51:41 Uhr schrieb Louis Epstein: >>>>>
As I said they were automatically filled in, probably tied to my being >>>>>> in / (I am familiar with unmounting any OTHER partition when doing fsck >>>>>> but how can I unmount the / when the OS is there?...since the system >>>>>> isn't responding to a crash how do I get into a different mode?)
You cant do fsck with repairs on a mounted file system. You need to boot >>>>> a live system (any distribution you like, e.g. Ubuntu) and run fsck
there. Then you should be able to change the contents on the file system >>>>> that is broken.
You can if it's mounted read only. At least, that's how you fix the root >>>> file system.
(problem now fixed)
How?
Doing a full fsck in single user mode (no journal).
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 379 |
Nodes: | 16 (2 / 14) |
Uptime: | 83:59:40 |
Calls: | 8,091 |
Files: | 13,069 |
Messages: | 5,851,128 |