In article ,
Michael van Elst wrote:
>ci4...@gmail.com (Chavdar Ivanov) writes:
>
>># tunefs -o time /dev/rdk5
>>tunefs: tuning /dev/rdk5
>>tunefs: optimization preference remains unchanged as time
>>tunefs: mount of /dev/dk1 on / updated <==
>
>If the device is "mounted", tunefs triggers a
ci4...@gmail.com (Chavdar Ivanov) writes:
># tunefs -o time /dev/rdk5
>tunefs: tuning /dev/rdk5
>tunefs: optimization preference remains unchanged as time
>tunefs: mount of /dev/dk1 on / updated <==
If the device is "mounted", tunefs triggers a mount -u to push
changes into the kernel.
On Thu, 6 Aug 2020 at 14:50, Thomas Klausner wrote:
>
> On Thu, Aug 06, 2020 at 01:21:34PM +0100, Chavdar Ivanov wrote:
> > On Thu, 6 Aug 2020 at 13:51, Thomas Klausner wrote:
> > >
> > > Hi!
> > >
> > > I've added a new disk and newfsed it. Then I ran tunefs and saw:
> > >
> > > # tunefs -o
On Thu, Aug 06, 2020 at 01:21:34PM +0100, Chavdar Ivanov wrote:
> On Thu, 6 Aug 2020 at 13:51, Thomas Klausner wrote:
> >
> > Hi!
> >
> > I've added a new disk and newfsed it. Then I ran tunefs and saw:
> >
> > # tunefs -o time /dev/rdk10
> > tunefs: tuning /dev/rdk10
> > tunefs: optimization
On Thu, 6 Aug 2020 at 13:51, Thomas Klausner wrote:
>
> Hi!
>
> I've added a new disk and newfsed it. Then I ran tunefs and saw:
>
> # tunefs -o time /dev/rdk10
> tunefs: tuning /dev/rdk10
> tunefs: optimization preference remains unchanged as time
> tunefs: mount: Invalid argument
$ uname -a
Hi!
I've added a new disk and newfsed it. Then I ran tunefs and saw:
# tunefs -o time /dev/rdk10
tunefs: tuning /dev/rdk10
tunefs: optimization preference remains unchanged as time
tunefs: mount: Invalid argument
I don't remember seeing this last line before.
9.99.69/amd64
Thomas
