On 2018-Jan-7, at 10:23 AM, blubee blubeeme <gurenchan atgmail.com> wrote:
> On Mon, Jan 8, 2018 at 1:41 AM, Mark Millard <markmi at dsl-only.net> wrote:
>> On 2018-Jan-7, at 7:50 AM, blubee blubeeme <gurenchan at gmail.com> wrote:
>> > I ran this test and here's some results.
>> > gstat -pd images:
>> > 18GB file from laptop to phone: https://imgur.com/a/7iHwv
>> > 18GB file from laptop to ssd: https://imgur.com/a/40Q6V
>> > multiple small files from laptop to phone: https://imgur.com/a/B4v4y
>> > multiple small files from laptop to ssd: https://imgur.com/a/mDiMu
>> > The files are missing timestamps but the originals were taken with scrot
>> > and have timestamps available here:
>> > https://nofile.io/f/mzKnkpM9CyC/stats.tar.gz2
>> > as far as why there's such high deletions? I can't say I'm only using cp.
>> I assume that md99 is for a file-based swap-space, such as
>> via /var/swap0 file. (As a side note I warn about bugzilla
>> 206048 for such contexts.) Otherwise please describe how
>> md99 is created. (Below I assume the swap-space usage of
>> The only other device that your pictures show is your
>> NVMe device nvd0.
>> No picture shows a device for the LG v30 when it is mentioned
>> above as being copied to or from. How is it that there is no
>> mounted device shown for the LG v30?
>> No picture shows a device for the SSD when it is mentioned
>> above as being copied to or from. How is it that there
>> is no mounted device shown for the SSD?
>> Without a device displayed for the LG-v30/SSD there is nothing
>> displayed for its reads or writes. This makes the gstat -pd
>> May be the p needs to be omitted for some reason? gstat -d
>> Mark Millard
>> markmi at dsl-only.net
> You are correct that md99 is a file backed swap disk, I am aware of the
> issues but I had to test some things out.
> Those tests earlier was a huge time sink.
> Here's the dmesg output from earlier:
> . . .
> I don't know why gstat isn't showing the info u are looking for.
> You said earlier that something was getting deleted,
> I don't know what could be causing that.
Those "deletes" are more commonly called TRIM on SSD's.
FreeBSD called them, BIO_DELETE as I remember.
Those deletes have nothing to do with umounting, deleteing
> I've provided tons of debug out, logs, pciconf, dmesg, etc...
> Even say forget the mobile device and go from
>From which I've not been able to figure out the kind of
information that I'm looking for.
Just because a device is present, does not mean that it
is available as a file system. I'm more interested in
how the file systems are made available --or if some
non-file system way of working is involved.
> Are you saying that there's something misconfigured on my end?
> What other info do you need me to provide to try to figure out
> what's going on or why I'm getting these transfer rates?
I'm saying I still can not tell how you make the SSD or the
LGv 30 available to FreeBSD (mount?). Or why no matching
mounted device shows up in gstat's display.
If you wish to keep trying to help me help you, . . .
Please show how you make the file system on the
SSD available to FreeBSD: what FreeBSD commands make
the device available for use. (I'd guess that mount
is used or that something like /etc/fstab is used
to do mounts more implicitly.)
Please show how you make the LG v30 available to FreeBSD:
what FreeBSD commands make the device available for
use. (I'd guess that mount is used or that something like
/etc/fstab is used to do mounts more implicitly.)
(I would expect these are mount commands, or at least
involve mount commands/calls. Some of the following makes
For each of those: with the device available show the
Similarly, show the exact commands used to make the
copies to and from the SSD. Show the exact commands
used to make the copies to and from the LG v30.
(You can for now stop the commands early or just
not start any that would take a long time.)
I'm looking for a way to get information similar to
what I expected gstat to show. I'd expect a mounted
file system but may be something else is involved?
markmi at dsl-only.net
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"