* Anyone know to fix "Exiting after unrecoverable error." using mkfs -t reiserfs /dev/sdbX
@ 2017-07-14 10:46 doiggl
2017-07-15 11:12 ` dimas
0 siblings, 1 reply; 3+ messages in thread
From: doiggl @ 2017-07-14 10:46 UTC (permalink / raw)
To: reiserfs-devel
Hello.
Anyone know to fix "Exiting after unrecoverable error." using mkfs -t
reiserfs /dev/sdb3
using mkfs.reiserfs 3.6.25
-error is repeatable:
--Glenn
# strace -e open mkfs -V -t reiserfs /dev/sdb3
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3
open("/usr/lib/locale/en_US.UTF-8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
open("/usr/lib/locale/en_US.utf8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = 3
open("/usr/lib64/gconv/gconv-modules.cache", O_RDONLY) = 3
mkfs from util-linux 2.23.2
mkfs.reiserfs /dev/sdb3
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
open("/usr/lib64/libreiserfscore.so.0", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libcom_err.so.2", O_RDONLY|O_CLOEXEC) = 3
open("/usr/lib64/libuuid.so.1", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3
mkfs.reiserfs 3.6.25
open("/dev/sdb3", O_RDONLY) = 3
open("/proc/mounts", O_RDONLY|O_CLOEXEC) = 3
open("/etc/mtab", O_RDONLY|O_CLOEXEC) = 3
Guessing about desired format.. Kernel 4.9.0-3-vanilla is running.
open("/dev/sdb3", O_RDONLY) = 3
open("/dev/sdb3", O_RDWR|O_EXCL) = 3
open("/dev/sdb3", O_RDWR) = 4
open("/dev/urandom", O_RDONLY|O_CLOEXEC) = 5
Format 3.6 with standard journal
Count of blocks on the device: 7079168
Number of blocks consumed by mkreiserfs formatting process: 8428
Blocksize: 4096
Hash function used to sort names: "r5"
Journal Size 8193 blocks (first block 18)
Journal Max transaction length 1024
inode generation number: 0
UUID: e6999e40-3421-4ddd-9033-d05a038746a6
ATTENTION: YOU SHOULD REBOOT AFTER FDISK!
ALL DATA WILL BE LOST ON '/dev/sdb3'!
Continue (y/n):y
Initializing journal - 0%....20%....40%....60%....80%....100%
Exiting after unrecoverable error.
+++ exited with 1 +++
#
# Tried ext4 -process worked.
#
# mkfs -t ext4 /dev/sdb3
mke2fs 1.42.8 (20-Jun-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1770720 inodes, 7079168 blocks
353958 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
217 block groups
32768 blocks per group, 32768 fragments per group
8160 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
# mount /dev/sdb3 /media/disk3
# umount /dev/sdb3
# Tried reiserfs again -process failed.
# mkfs -t reiserfs /dev/sdb3
mkfs.reiserfs 3.6.25
Guessing about desired format.. Kernel 4.9.0-3-vanilla is running.
Format 3.6 with standard journal
Count of blocks on the device: 7079168
Number of blocks consumed by mkreiserfs formatting process: 8428
Blocksize: 4096
Hash function used to sort names: "r5"
Journal Size 8193 blocks (first block 18)
Journal Max transaction length 1024
inode generation number: 0
UUID: d867e985-b90a-438d-ba8d-e5a2e4bf699f
ATTENTION: YOU SHOULD REBOOT AFTER FDISK!
ALL DATA WILL BE LOST ON '/dev/sdb3'!
Continue (y/n):y
Initializing journal - 0%....20%....40%....60%....80%....100%
Exiting after unrecoverable error.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Anyone know to fix "Exiting after unrecoverable error." using mkfs -t reiserfs /dev/sdbX
2017-07-14 10:46 Anyone know to fix "Exiting after unrecoverable error." using mkfs -t reiserfs /dev/sdbX doiggl
@ 2017-07-15 11:12 ` dimas
2017-07-17 14:04 ` doiggl
0 siblings, 1 reply; 3+ messages in thread
From: dimas @ 2017-07-15 11:12 UTC (permalink / raw)
To: reiserfs-devel
did you try to zero-wipe the partition?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Anyone know to fix "Exiting after unrecoverable error." using mkfs -t reiserfs /dev/sdbX
2017-07-15 11:12 ` dimas
@ 2017-07-17 14:04 ` doiggl
0 siblings, 0 replies; 3+ messages in thread
From: doiggl @ 2017-07-17 14:04 UTC (permalink / raw)
To: reiserfs-devel, dimas000
On Sat, 15 Jul 2017 14:12:02 +0300, dimas <dimas000@ya.ru> wrote:
> did you try to zero-wipe the partition?
> --
> To unsubscribe from this list: send the line "unsubscribe
reiserfs-devel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello,
Question :did you try to zero-wipe the partition?
Answr: no - unknown
What is command switch to do that ? [zero-wipe the partition]?
Tried to use but no luck:
# mkfs -t reiserfs /dev/sdb3
Thanks
--Glenn
# mkfs --help
Usage:
mkfs [options] [-t <type>] [fs-options] <device> [<size>]
Options:
-t, --type=<type> filesystem type; when unspecified, ext2 is used
fs-options parameters for the real filesystem builder
<device> path to the device to be used
<size> number of blocks to be used on the device
-V, --verbose explain what is being done;
specifying -V more than once will cause a dry-run
-V, --version display version information and exit;
-V as --version must be the only option
-h, --help display this help text and exit
For more information see mkfs(8).
#
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-07-17 14:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-07-14 10:46 Anyone know to fix "Exiting after unrecoverable error." using mkfs -t reiserfs /dev/sdbX doiggl
2017-07-15 11:12 ` dimas
2017-07-17 14:04 ` doiggl
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).