25.02.2020 4:37, Minoru TANABE wrote:
CC'ing to author of mentioned revision.
> Hi, all.
> I'm 12-stable user.
> My system upgrade from 12.1-stable_r357351(2020-02-01) to
> r358294(2020-02-24).
> After upgrading, I can't input '\', '|', '_' symbol.
>
> I use vt console driver and jp.capsctrl.kbd
Hi Mike, thanks for the insight.
I tried both, but not at the same time.
When I found that the ZFS was corrupting the filesystem, I reinstalled the
FreeBSD using UFS but no luck.
Ulf told me that he had the same problem and it turned out the problem was
a defective RAM, but here I just ran the tes
Mario, have you ruled out the possibility that the UFS and ZFS filesystems
are overlapping? It would be worth a careful check of the partition table
and filesystem sizes. You can check the actual UFS size with dumpfs.
I ask in part because UFS has a tendency to write to the last cylinder
group.
>From mike Sun Feb 23 17:24:54 2020
Received: from mx2.freebsd.org (mx2.freebsd.org [96.47.72.81])
by mail.karels.net (8.15.2/8.15.2) with ESMTP id 01NNOsPX085694
for ; Sun, 23 Feb 2020 17:24:54 -0600 (CST)
(envelope-from owner-freebsd-sta...@freebsd.org)
Received: from mx1
Hi, all.
I'm 12-stable user.
My system upgrade from 12.1-stable_r357351(2020-02-01) to
r358294(2020-02-24).
After upgrading, I can't input '\', '|', '_' symbol.
I use vt console driver and jp.capsctrl.kbd keymap.
These symbols are defined as scancode 115 and 125 in keymap.
I checked source, and fi
On Mon, Feb 24, 2020 at 3:56 PM Mario Olofo wrote:
> Hi Matt,
>
> The ext4 don't have data checksum, but have metadata checksum, which would
> probably be corrupted as well, as I reinstalled my Linux over the same
> partition the FreeBSD was using, and by
> now I have a lot more files on it than
Hi Matt,
The ext4 don't have data checksum, but have metadata checksum, which would
probably be corrupted as well, as I reinstalled my Linux over the same
partition the FreeBSD was using, and by
now I have a lot more files on it than I had on FreeBSD.
If you look at the forum post I created, you'l
On Mon, Feb 24, 2020 at 2:44 PM Mario Olofo wrote:
> Hi Pete, in the logs there's nothing wrong, I only see the problem on zpool
> status after the first scrub, even if I just
> reinstall the FreeBSD and some basic packages (didn't even need a lot of
> files as I thought).
Mario,
Out of curios
Hi Pete, in the logs there's nothing wrong, I only see the problem on zpool
status after the first scrub, even if I just
reinstall the FreeBSD and some basic packages (didn't even need a lot of
files as I thought).
Hello Rebecca, indeed is this model I'm using, the SATA versions is cheaper
so I in
On 2/24/20 12:13 PM, Mario Olofo wrote:
root@~ # camcontrol devlist
at scbus0 target 0 lun 0 (ada0,pass0)
at scbus1 target 0 lun 0 (ada1,pass1)
at scbus2 target 0 lun 0 (pass2,da0)
Ok, so it's a SATA M.2 SSD - one of these:
https://shop.westerndigital.com/products/inte
On 2020-02-24 11:13, Mario Olofo wrote:
Hi Pete,
The nvmecontrol devlist don't found any devices.
pciconf -lv nvme0 didn't found anything either.
The camcontrol devlist output was as follows:
root@~ # camcontrol devlist
at scbus0 target 0 lun 0 (ada0,pass0)
at scbus1 target 0 lun
Hi Pete,
The nvmecontrol devlist don't found any devices.
pciconf -lv nvme0 didn't found anything either.
The camcontrol devlist output was as follows:
root@~ # camcontrol devlist
at scbus0 target 0 lun 0 (ada0,pass0)
at scbus1 target 0 lun 0 (ada1,pass1)
at scbus2 target
On 2020-02-24 09:58, Mario Olofo wrote:
Hello John, thank you for your reply.
Yesterday I reinstalled the 12.1 on a VirtualBox virtual machine, did the
same steps and it didn't corrupted the ZFS, so I think that the problem is
in the FreeBSD's driver for m.2 SSD.
Besides the corruption of the
Hello John, thank you for your reply.
Yesterday I reinstalled the 12.1 on a VirtualBox virtual machine, did the
same steps and it didn't corrupted the ZFS, so I think that the problem is
in the FreeBSD's driver for m.2 SSD.
Besides the corruption of the filesystem, I forgot to mention that I
notic
On Sun, Feb 23, 2020 at 11:18:08PM -0300, Mario Olofo wrote:
> Some time ago I tried to switch from Linux to FreeBSD 12.1, used a WiFi
> dongle and all good, until I found that both ZFS and UFS corrupted the
> filesystem very fast.
> I work with a lot of small files because of web programming (node
15 matches
Mail list logo
