Date: Sat, 17 Feb 2024 11:04:06 -0800 From: Mark Millard <marklmi@yahoo.com> To: Mike Karels <mike@karels.net>, Ordinary Bit <ordinarybit@proton.me> Cc: Ronald Klop <ronald-lists@klop.ws>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: newfs TRIM flag device support Message-ID: <9F657059-E39A-4E2A-8AF5-CA491BBC7ABB@yahoo.com> In-Reply-To: <F12979C1-55EF-4AC3-88D9-5CE7236F3AD3@karels.net> References: <zBjNO8pJgkvHeMFBa74-f89m7IO_mgcHccwonGg0sZNJtDds49EICbFezJwbGJYnQDSVEI_tm3vCG4pjpdwiNyAtfF9lYfAn9znBR2I0AMQ=@proton.me> <8D8AA3F5-74A3-4AFE-A560-F52C7C55CF12@yahoo.com> <7okx4eDPse2uF1n3aX4W8RIOdbHXziUhqgvHxqqxpYN-7NsJfEGrfHbDxLgNS3PdOwZt7j9aOXp-0MHDjQAryL4t1Gd2QHUG1sFNmd5dY0k=@proton.me> <454941689.1180.1708079489598@localhost> <VCao0qH9-9Ie88pJtfOTzurWaPFxGEKRaZZL8zSjKaaM2hEQIB8R1p8kB7Cc7PvB7NK0Df0XrDamMZFx3PJlT85t6QVBm4T0leqvJA0MdF4=@proton.me> <nMflyJQojjrvtvJlZ2Re4YFpszk2lUaFkiZjtWguBRzji81TTjSKq-1z-PTZrYhW33lARfF0CPs0Nck4z3yQEH6pjLFKOt91F8NiLKogOQQ=@proton.me> <59693EE7-0DD6-4B41-BA64-0F3D69D3ECC9@yahoo.com> <bVPrJeknNzb33PLpaM2c4eJyCtFuENc2rqG2-n-9Za44UOyMq5Ot15UYC0JMckCYvlQ-n0IejdSlMEUcTfp0OeaSqR4dWCYGc7Z-a7CdkdE=@proton.me> <1B0C2E27-6776-40A1-A8BF-29094FF8FC03@yahoo.com> <zlZ2Mri1Mx99HOY1z1WXazEOCID5CWKwwmgvOVYDCmxWwSyxpK1LIZfvFcUPN9-aV9AVskZ9lMiUXNCHTZaPK1wz-KTEKtmZdyVbksSfJ90=@proton.me> <F12979C1-55EF-4AC3-88D9-5CE7236F3AD3@karels.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 17, 2024, at 08:44, Mike Karels <mike@karels.net> wrote:
> On 17 Feb 2024, at 10:21, Ordinary Bit wrote:
>=20
>> On Saturday, 17 February 2024 at 23:20, Mark Millard =
<marklmi@yahoo.com> wrote:
>>=20
>>> On Feb 17, 2024, at 02:39, Ordinary Bit ordinarybit@proton.me wrote:
>>> . . .=20
>>>>=20
>>>> root@sd-ultra:~ # gpart show -p
>>>> =3D> 63 124735425 mmcsd0 MBR (59G)
>>>> 63 1985 - free - (993K)
>>>> 2048 102400 mmcsd0s1 fat32lba [active] (50M)
>>>> 104448 10381312 mmcsd0s2 freebsd (5.0G)
>>>> 10485760 16777216 mmcsd0s3 freebsd (8.0G)
>>>=20
>>>=20
>>> An oddity just above is that mmcsd0s3 is not set to the
>>> type freebsd-ufs . But the oddity does not mess up the
>>> testing you were doing.
>>>=20
>>=20
>> Let me test this one with freebsd-ufs type because you're right it's =
only freebsd.
>=20
> freebsd-ufs is a GPT type; this is MBR. The ufs filesystem is =
presumably mmcsd0s3a.
> If the filesystem gets mounted, the partitioning is OK.
>=20
> Mike
>=20
>>>> 27262976 97472512 - free - (46G)
>>>>=20
>>>> =3D> 0 10381312 mmcsd0s2 BSD (5.0G)
>>>> 0 128 - free - (64K)
>>>> 128 10381184 mmcsd0s2a freebsd-ufs (4.9G)
>>>> . . .
>=20
My splitting of the gpart output at the line I was interested in
may have left some confusion. So I'll quote the original full
output. I was not very explicit about the details of the oddities
involved before but will be so below.
QUOTE
root@sd-ultra:~ # gpart show -p
=3D> 63 124735425 mmcsd0 MBR (59G)
63 1985 - free - (993K)
2048 102400 mmcsd0s1 fat32lba [active] (50M)
104448 10381312 mmcsd0s2 freebsd (5.0G)
10485760 16777216 mmcsd0s3 freebsd (8.0G)
27262976 97472512 - free - (46G)
=3D> 0 10381312 mmcsd0s2 BSD (5.0G)
0 128 - free - (64K)
128 10381184 mmcsd0s2a freebsd-ufs (4.9G)
END QUOTE
First note that mmcsd0s2a says freebsd-ufs (but is
inside a BSD). That is what I consider normal for MBR
partitions that contain UFS file systems.
Next note that there was no "mmcsd0s3 BSD" shown.
Nor was there a "mmcsd0s3a freebsd-ufs" shown.
"mmcsd0s3 freebsd" shows no evidence of any MBR/BSD
substructure. (But it was mountable as a UFS file
system after the newfs that was done on mmcsd0s3 .)
None of this messed up the testing that was being
done.
=3D=3D=3D
Mark Millard
marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9F657059-E39A-4E2A-8AF5-CA491BBC7ABB>