Re: Removing fdisk and bsdlabel (legacy partition tools)

Am 2024-01-25 18:49, schrieb Rodney W. Grimes: On Thu, Jan 25, 2024, 9:11?AM Ed Maste wrote: > On Thu, 25 Jan 2024 at 11:00, Rodney W. Grimes > wrote: > > > > > These will need to be addressed before actually removing any of these > > > binaries, of course. > > > > You seem to have missed

Re: Removing fdisk and bsdlabel (legacy partition tools)

On Thu, 25 Jan 2024 at 17:26, Robert R. Russell wrote: > > FYI gpart doesn't allow you to create disklabel with more than 8 items > either. Specify the number of partitions at `gpart create` time: # mdconfig -s 1G -t swap md0 # gpart create -s bsd -n 20 md0 md0 created # for i in $(jot 19); do

make buildworld failure on arm64 on -current n267777

In /usr/src # git rev-list --count --first-parent HEAD 26 include/machine -> /usr/src/sys/arm64/include Building /usr/obj/usr/src/arm64.aarch64/stand/efi/loader_4th/vers.c Building /usr/obj/usr/src/arm64.aarch64/stand/efi/loader_4th/8x16.c Building

Re: Removing fdisk and bsdlabel (legacy partition tools)

On Wed, 24 Jan 2024 10:44:57 -0500 Ed Maste wrote: > MBR (PC BIOS) partition tables were historically maintained with > fdisk(8), but gpart(8) has long been the preferred method for working > with partition tables of all types. fdisk has been declared as > obsolete in the man page since 2015.

Re: Removing fdisk and bsdlabel (legacy partition tools)

In message <20240125101308.92e93...@slippy.cwsent.com>, Cy Schubert writes: > In message <84c6f3b1-58b3-44f8-aeaf-35f78e059...@quip.cz>, Miroslav Lachman > wri > tes: > > On 25/01/2024 06:50, Cy Schubert wrote: > > > In message > > > l. > > c > > > > > > >> > > >> What can they do that gpart

Re: Removing fdisk and bsdlabel (legacy partition tools)

> On Thu, Jan 25, 2024, 9:11?AM Ed Maste wrote: > > > On Thu, 25 Jan 2024 at 11:00, Rodney W. Grimes > > wrote: > > > > > > > These will need to be addressed before actually removing any of these > > > > binaries, of course. > > > > > > You seem to have missed /rescue. Now think about that

Re: Removing fdisk and bsdlabel (legacy partition tools)

On Jan 25, 2024, at 8:15 AM, Warner Losh wrote: > > What can fdisk and/or disklabel repair that gpart can't? May be add a section in gpart that shows how to map fdisk & bsdlabel functionality to gpart? Better still, why not provide scripts for fdisk/bsdlabel that use gpart underneath? FreeBSD

Re: Removing fdisk and bsdlabel (legacy partition tools)

On Thu, Jan 25, 2024, 9:11 AM Ed Maste wrote: > On Thu, 25 Jan 2024 at 11:00, Rodney W. Grimes > wrote: > > > > > These will need to be addressed before actually removing any of these > > > binaries, of course. > > > > You seem to have missed /rescue. Now think about that long > > and hard,

Re: Removing fdisk and bsdlabel (legacy partition tools)

On Thu, 25 Jan 2024 at 11:00, Rodney W. Grimes wrote: > > > These will need to be addressed before actually removing any of these > > binaries, of course. > > You seem to have missed /rescue. Now think about that long > and hard, these tools classified as so important that they > are part of

Re: Re: Removing fdisk and bsdlabel (legacy partition tools)

On Thu, 25 Jan 2024 at 10:50, Mina Galić wrote: > > i was looking at cd(4) today, and to my surprise, it was full of disklabel > references. Oh, indeed - as with the old references in ccd(4) that should go. The last reference to `struct disklabel` in the CAM SCSI cd driver was removed over two

Re: Removing fdisk and bsdlabel (legacy partition tools)

> On Wed, 24 Jan 2024 at 12:30, Warner Losh wrote: > > > > Those are the only users in the tree, but not for long :) > > I have some reviews open to remove some old fdisk / diskabel / > bsdlabel invocations from the tree. > > With those applied, for fdisk I see the following references >

Re: Re: Removing fdisk and bsdlabel (legacy partition tools)

> > Those are the only users in the tree, but not for long :) > > I have some reviews open to remove some old fdisk / diskabel / > bsdlabel invocations from the tree. > > With those applied, for fdisk I see the following references > (excluding sbin/fdisk/* and comments, old examples,

Re: Removing fdisk and bsdlabel (legacy partition tools)

On Wed, 24 Jan 2024 at 12:30, Warner Losh wrote: > > Those are the only users in the tree, but not for long :) I have some reviews open to remove some old fdisk / diskabel / bsdlabel invocations from the tree. With those applied, for fdisk I see the following references (excluding sbin/fdisk/*

Re: loading vmm.ko crashes main-n267684-e4b646ce1610

On Thu, Jan 25, 2024 at 03:34:54PM +0800, Zhenlei Huang wrote: You may want to configure the dump device before get the coredump. See https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/#kerneldebug-obtain

Re: Removing fdisk and bsdlabel (legacy partition tools)

In message <84c6f3b1-58b3-44f8-aeaf-35f78e059...@quip.cz>, Miroslav Lachman wri tes: > On 25/01/2024 06:50, Cy Schubert wrote: > > In message c > > > >> > >> What can they do that gpart can't do? > > > > This was quite a while ago, booted off my recovery USB attempting to repair > > some self

Re: Removing fdisk and bsdlabel (legacy partition tools)

In message <2369865.bDOn7JOVgO@ravel>, Olivier Certner writes: > --nextPart5823302.8T7jmnknE8 > Content-Transfer-Encoding: 7Bit > Content-Type: text/plain; charset="UTF-8"; protected-headers="v1" > From: Olivier Certner > To: Cy Schubert > Subject: Re: Removing fdisk and bsdlabel (legacy

Re: Removing fdisk and bsdlabel (legacy partition tools)

Quoting Cy Schubert : In message , Warner Losh writes: --b0adc9060fbe7411 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jan 24, 2024, 10:07=E2=80=AFPM Cy Schubert wrote: > In message

Re: Removing fdisk and bsdlabel (legacy partition tools)

On 25/01/2024 06:50, Cy Schubert wrote: In message What can they do that gpart can't do? This was quite a while ago, booted off my recovery USB attempting to repair some self caused damage. The ability to edit (vi) a file with starting addresses and lengths, visually using bsdlabel, was

Re: Removing fdisk and bsdlabel (legacy partition tools)

Hi, > A visual view of columns of a bsdlabel, editing a label using vi, checking > and double checking numbers before committing them is handy.The visual > format and the ability to adjust the numbers in an editor before committing > them is handy. You can't do this with gpart, as it's

Re: loading vmm.ko crashes main-n267684-e4b646ce1610

> On Jan 24, 2024, at 8:47 AM, void wrote: > > Hello, > > Loading vmm either via vmm_load=YES in /boot/loader.conf or > manually via kldload vmm crashes the system to db> prompt > as shown in the link below: > > http://void.f-m.fm.user.fm/Screenshot_20240122_135539.png > > Thing is, access

Re: Removing fdisk and bsdlabel (legacy partition tools)

Ed Maste wrote: > I would like to disconnect these from the build, and subsequently > remove them. I'm in favour of this change. Having different tools (some modern and updated, others deprecated and limited) in base to do the same task can confuse the users. If possible move them to ports for

Re: Removing fdisk and bsdlabel (legacy partition tools)

In message , Warner Losh writes: > --b0adc9060fbe7411 > Content-Type: text/plain; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > > On Wed, Jan 24, 2024, 10:07=E2=80=AFPM Cy Schubert om> > wrote: > > > In message <202401242347.40onlwkz099...@gndrsh.dnsmgr.net>,

Re: Removing fdisk and bsdlabel (legacy partition tools)

On Wed, Jan 24, 2024, 10:07 PM Cy Schubert wrote: > In message <202401242347.40onlwkz099...@gndrsh.dnsmgr.net>, "Rodney W. > Grimes" > writes: > > > I would agree personally, to moving to ports (eg ports/sysutils) with > > > a DEPRECATED in the DESCR or something, or better yet a Make > > >

Re: Removing fdisk and bsdlabel (legacy partition tools)

In message , "Patrick M. Hause n" writes: > Hi all, > > > Am 25.01.2024 um 00:47 schrieb Rodney W. Grimes = > : > >=20 > >> I would agree personally, to moving to ports (eg ports/sysutils) with > >> a DEPRECATED in the DESCR or something, or better yet a Make > >> invokation event to say

Re: Removing fdisk and bsdlabel (legacy partition tools)

In message <202401242347.40onlwkz099...@gndrsh.dnsmgr.net>, "Rodney W. Grimes" writes: > > I would agree personally, to moving to ports (eg ports/sysutils) with > > a DEPRECATED in the DESCR or something, or better yet a Make > > invokation event to say "superceded, here is how to proceed against

Re: Removing fdisk and bsdlabel (legacy partition tools)

Hi all, > Am 25.01.2024 um 00:47 schrieb Rodney W. Grimes > : > >> I would agree personally, to moving to ports (eg ports/sysutils) with >> a DEPRECATED in the DESCR or something, or better yet a Make >> invokation event to say "superceded, here is how to proceed against >> advice") or

Re: Removing fdisk and bsdlabel (legacy partition tools)

> I would agree personally, to moving to ports (eg ports/sysutils) with > a DEPRECATED in the DESCR or something, or better yet a Make > invokation event to say "superceded, here is how to proceed against > advice") or something. They are totally useless as ports when your booted from install

Re: Error while linking bsdinstall

On 19/01/2024 18:33, Fernando Apesteguía wrote: Hi all, I'm having a problem linking bsdinstall in current dfe30e41967f9b5112c42ca20ec2c366db74cef9 ld: error: undefined symbol: bsddialog_clear >>> referenced by part_wizard.c:76

Re: Removing fdisk and bsdlabel (legacy partition tools)

Killing these would be excellent. I have not used either in many years for either MBR or GPT. The first time used gpart on an MBR disc, I realized that fdisk and bsdlabel, which I'd always found rather clunky, should die, but for years I kept seeing people claim that gpart was only for GPT and

Re: Removing fdisk and bsdlabel (legacy partition tools)

On Wed, Jan 24, 2024 at 6:30 PM Warner Losh wrote: The in-kernel gpart copes so much better. > (..) > I wouldn't object to making these ports (..) +1 for moving fdisk and bsdlabel to ports instead deleting :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Re: Removing fdisk and bsdlabel (legacy partition tools)

I would agree personally, to moving to ports (eg ports/sysutils) with a DEPRECATED in the DESCR or something, or better yet a Make invokation event to say "superceded, here is how to proceed against advice") or something. -G On Thu, Jan 25, 2024 at 3:30 AM Warner Losh wrote: > > On Wed, Jan 24,

Re: Removing fdisk and bsdlabel (legacy partition tools)

On 24/01/2024 19:50, Rodney W. Grimes wrote: On Wed, Jan 24, 2024 at 8:45?AM Ed Maste wrote: MBR (PC BIOS) partition tables were historically maintained with fdisk(8), but gpart(8) has long been the preferred method for working with partition tables of all types. fdisk has been declared as

Re: Removing fdisk and bsdlabel (legacy partition tools)

Ed Maste wrote: > MBR (PC BIOS) partition tables were historically maintained with > fdisk(8), but gpart(8) has long been the preferred method for working > with partition tables of all types. fdisk has been declared as > obsolete in the man page since 2015. Similarly BSD disklabels were >

Re: Removing fdisk and bsdlabel (legacy partition tools)

On 24 Jan 2024, at 12:50, Rodney W. Grimes wrote: >> On Wed, Jan 24, 2024 at 8:45?AM Ed Maste wrote: >> >>> MBR (PC BIOS) partition tables were historically maintained with >>> fdisk(8), but gpart(8) has long been the preferred method for working >>> with partition tables of all types. fdisk has

Re: Removing fdisk and bsdlabel (legacy partition tools)

In message , Ed Maste writes: > MBR (PC BIOS) partition tables were historically maintained with > fdisk(8), but gpart(8) has long been the preferred method for working > with partition tables of all types. fdisk has been declared as > obsolete in the man page since 2015. Similarly BSD disklabels

Re: Removing fdisk and bsdlabel (legacy partition tools)

> On Wed, Jan 24, 2024 at 8:45?AM Ed Maste wrote: > > > MBR (PC BIOS) partition tables were historically maintained with > > fdisk(8), but gpart(8) has long been the preferred method for working > > with partition tables of all types. fdisk has been declared as > > obsolete in the man page since

Re: Removing fdisk and bsdlabel (legacy partition tools)

Ed Maste writes: > MBR (PC BIOS) partition tables were historically maintained with > fdisk(8), but gpart(8) has long been the preferred method for working > with partition tables of all types. fdisk has been declared as > obsolete in the man page since 2015. Similarly BSD disklabels

Re: Removing fdisk and bsdlabel (legacy partition tools)

On Wed, Jan 24, 2024 at 8:45 AM Ed Maste wrote: > MBR (PC BIOS) partition tables were historically maintained with > fdisk(8), but gpart(8) has long been the preferred method for working > with partition tables of all types. fdisk has been declared as > obsolete in the man page since 2015.

Removing fdisk and bsdlabel (legacy partition tools)

MBR (PC BIOS) partition tables were historically maintained with fdisk(8), but gpart(8) has long been the preferred method for working with partition tables of all types. fdisk has been declared as obsolete in the man page since 2015. Similarly BSD disklabels were historically maintained with

loading vmm.ko crashes main-n267684-e4b646ce1610

Hello, Loading vmm either via vmm_load=YES in /boot/loader.conf or manually via kldload vmm crashes the system to db> prompt as shown in the link below: http://void.f-m.fm.user.fm/Screenshot_20240122_135539.png Thing is, access is via a html5 console with no up/down scrolling or buffer. Nothing

Re: vmm_load crashes to debugger early

Hi, On Mon, 22 Jan 2024, at 12:48, Ronald Klop wrote: > Hi, > > Can you mount /boot on another system? not sure how as the system cannot find the pool called 'zroot'. There are two zpools on the server - zroot for HD and 'ssd' for the ssds. I can boot to -current usb stick and zpool import -f

Re: vmm_load crashes to debugger early

Hi, Can you mount /boot on another system? Can you press a key to interrupt booting the kernel? I'm not sure what the name of this stage of the booting is called and if it depends on which bootloader you are using. In my VM I get this on the text "Beastie"-menu with the text: "Autoboot in

vmm_load crashes to debugger early

Hello, On a very recent -current, vmm_load="YES" in /boot/loader.conf crashes the system to debugger early on in the boot sequence. I can't even reach single user mode How can I prevent this one element of /boot/loader.conf from loading? thanks in advance for any advice --

SDHCI_QUIRK_BROKEN_SDMA_BOUNDARY, maxphys, SDHCI_BLKSZ_SDMA_BNDRY_512K, and alloc_bounce_zone behavior [RPi5 example]

I had previously reported on the freebsd-arm list that on the RPi5 used via the EDK2 draft I was seeing: # sysctl hw.busdma hw.busdma.zone0.total_deferred_time: 0 0 hw.busdma.zone0.domain: 0 hw.busdma.zone0.alignment: 524288 hw.busdma.zone0.lowaddr: 0x hw.busdma.zone0.total_deferred: 0

Error while linking bsdinstall

Hi all, I'm having a problem linking bsdinstall in current dfe30e41967f9b5112c42ca20ec2c366db74cef9 ld: error: undefined symbol: bsddialog_clear >>> referenced by part_wizard.c:76 (/data/fernape_data/FreeBSD-repos/src/usr.sbin/bsdinstall/partedit/part_wizard.c:76) >>>

Re: Alder lake supported? (graphics)

On 2024-01-18 15:42, Chris wrote: On 2024-01-18 15:28, Chris wrote: On 2024-01-18 08:47, Jan Beich wrote: Chris writes: On 2024-01-16 19:02, Jan Beich wrote: Chris writes: I upgraded to an alder lake based machine and installed 14. But I can't seem to get the intel graphics loaded

Re: Alder lake supported? (graphics)

On 2024-01-18 15:28, Chris wrote: On 2024-01-18 08:47, Jan Beich wrote: Chris writes: On 2024-01-16 19:02, Jan Beich wrote: Chris writes: I upgraded to an alder lake based machine and installed 14. But I can't seem to get the intel graphics loaded (drm-515-kmod). It simply freezes at

Re: Alder lake supported? (graphics)

On 2024-01-18 08:47, Jan Beich wrote: Chris writes: On 2024-01-16 19:02, Jan Beich wrote: Chris writes: I upgraded to an alder lake based machine and installed 14. But I can't seem to get the intel graphics loaded (drm-515-kmod). It simply freezes at load. Are Alder lake graphics

Re: How to upgrade an EOL FreeBSD release or how to make it working again

On Wed, Jan 17, 2024 at 3:54 PM Mario Marietto wrote: > Hello to everyone. > > I'm trying to copy the Chromebook's SNOW source files that have been included > on the FreeBSD 11 > revision 269385 to the new FreeBSD 13 revision 373300. It has compiled > correctly world,but when it > starts to

Re: Alder lake supported? (graphics)

Chris writes: > On 2024-01-16 19:02, Jan Beich wrote: > >> Chris writes: >> >>> I upgraded to an alder lake based machine and installed 14. >>> But I can't seem to get the intel graphics loaded (drm-515-kmod). >>> It simply freezes at load. >>> Are Alder lake graphics supported? >> Try

Re: How to upgrade an EOL FreeBSD release or how to make it working again

Hello to everyone. I'm trying to copy the Chromebook's SNOW source files that have been included on the FreeBSD 11 revision 269385 to the new FreeBSD 13 revision 373300. It has compiled correctly world,but when it starts to compile the kernel,it gives a lot of "unknown option" errors. Is there a

Re: Alder lake supported? (graphics)

On 2024-01-16 19:02, Jan Beich wrote: Chris writes: I upgraded to an alder lake based machine and installed 14. But I can't seem to get the intel graphics loaded (drm-515-kmod). It simply freezes at load. Are Alder lake graphics supported? Try drm-61-kmod instead (with

Re: How does one actually update ACPICA?

Op wo 17 jan 2024 om 10:53 schreef Idwer Vollering : > > Hi all, > > When attempting to build a newer release of ACPICA, it seems some > documentation is missing, or some steps are missing. I have consulted > the wiki whether updating instructions exist. > > The copyright header in

How does one actually update ACPICA?

Hi all, When attempting to build a newer release of ACPICA, it seems some documentation is missing, or some steps are missing. I have consulted the wiki whether updating instructions exist. The copyright header in sys/contrib/dev/acpica/common/acfileio.c hints I need the file

Re: Alder lake supported? (graphics)

Chris writes: > I upgraded to an alder lake based machine and installed 14. > But I can't seem to get the intel graphics loaded (drm-515-kmod). > It simply freezes at load. > Are Alder lake graphics supported? Try drm-61-kmod instead (with gpu-firmware-intel-kmod-alderlake >= 20230625).

Re: Alder lake supported? (graphics)

In message , Chris writes: >I upgraded to an alder lake based machine and installed 14. >But I can't seem to get the intel graphics loaded (drm-515-kmod). >It simply freezes at load. Shot in the dark: # pkg delete drm-515-kmod && pkg install drm-510-kmod && kldload i915kms John groenv...@acm.org

Alder lake supported? (graphics)

I upgraded to an alder lake based machine and installed 14. But I can't seem to get the intel graphics loaded (drm-515-kmod). It simply freezes at load. Are Alder lake graphics supported? releng/14.0-n265380-f9716eee8ab4 12th Gen Intel(R) Core(TM) i3-1215U vgapci0@pci0:0:2:0: class=0x03

Re: noatime on ufs2

Chris wrote in <9155214edb61b1bc3bad3bc96f96e...@bsdforge.com>: ... |I haven't seen anything in this thread that wouldn't be better placed in |tuning(7) |or tunefs(8). | |* Silicon disks fail without warning | tapes did as well. Unless you're working with punch cards please \ |

Re: Request for Testing: TCP RACK

W dniu 17.11.2023 o 00:13, tue...@fh-muenster.de pisze: On Nov 16, 2023, at 17:50, Marek Zarychta wrote: W dniu 16.11.2023 o 10:13, tue...@freebsd.org pisze: Dear all, recently the main branch was changed to build the TCP RACK stack which is a loadable kernel module, by default:

Re: suspend to idle support

16.01.24 20:29, Warner Losh: On Mon, Jan 15, 2024 at 10:24 AM Oleksandr Kryvulia wrote: Hello, What is a status of support suspend to idle? I found only two related reviews D17675 and D17676 and no more any information. It is a very desirable thing on modern laptops, where

Re: suspend to idle support

On Mon, Jan 15, 2024 at 10:24 AM Oleksandr Kryvulia wrote: > Hello, > What is a status of support suspend to idle? I found only two related > reviews D17675 and D17676 and no more any information. It is a very > desirable thing on modern laptops, where s3 is not supported like my X1 > Carbon

Re: noatime on ufs2

On 2024-01-09 00:47, Olivier Certner wrote: Why not make noatime the default across the whole system? Outside of mbox why is recording access time actually useful? Exactly. I've never found any compelling reason in most uses to enable "atime", except perhaps local mail but as addressed in

Re: How to upgrade an EOL FreeBSD release or how to make it working again

Old packages are not retained after EOL, but ports are version agnostic (more or less, as the current ports tree is only ar tested to run on supported versions and some are marked as "BROKEN" for some versions). All ports are available from the GIT repo (cgit.freebsd.org). On Mon, Jan 15, 2024 at

Re: NFSv4 crash of CURRENT

On Mon, Jan 15, 2024 at 11:03 AM FreeBSD User wrote: > > Am Mon, 15 Jan 2024 11:53:31 +0100 > Peter Blok schrieb: > > > Hi, > > > > Forgot to mention I’m on 13-stable. The fix that is causing the crash with > > automounted NFS > > is: > > > > commit cc5cda1dbaa907ce52074f47264cc45b5a7d6c8b > >

Re: How to upgrade an EOL FreeBSD release or how to make it working again

Hello. Do you have deleted forever the set of packages and ports for FreeBSD 11 or you keep them stored in DVDs that I can buy or download for a small amount of money ? If yes,where ? To rebuild everything is out of my expertise. On Mon, Jan 15, 2024 at 7:15 PM David Chisnall wrote: > On 15

Re: How to upgrade an EOL FreeBSD release or how to make it working again

On 15 Jan 2024, at 16:46, Mario Marietto wrote: > > The ARM Chromebook is based on armv7,it is still recent. For reference, the ARMv7 architecture was introduced in 2005. The last cores that implemented the architecture were released in 2014. This is not a ‘recent’ architecture, it’s one

suspend to idle support

Hello, What is a status of support suspend to idle? I found only two related reviews D17675 and D17676 and no more any information. It is a very desirable thing on modern laptops, where s3 is not supported like my X1 Carbon gen11[1]. [1] https://wiki.freebsd.org/Laptops/Thinkpad_X1_Carbon

Re: How to upgrade an EOL FreeBSD release or how to make it working again

The ARM Chromebook is based on armv7,it is still recent. But let's change perspective for a moment,don't think about the ARM Chromebook. My question is : how to upgrade FreeBSD when it goes EOL. I ask this because there is a huge difference here between FreeBSD and Linux. Today if you need to use

Re: NFSv4 crash of CURRENT

Am Mon, 15 Jan 2024 16:59:07 +0100 Peter Blok schrieb: > Rick, > > I can confirm Kostik’s fix works on 13-stable. > > Peter Me, too. The patch fixed the reported problem. Thank you very much. oh > > > On 15 Jan 2024, at 16:13, Peter Blok wrote: > > > > I can give it a shot on one of my

Re: NFSv4 crash of CURRENT

Am Mon, 15 Jan 2024 11:53:31 +0100 Peter Blok schrieb: > Hi, > > Forgot to mention I’m on 13-stable. The fix that is causing the crash with > automounted NFS > is: > > commit cc5cda1dbaa907ce52074f47264cc45b5a7d6c8b > Author: Konstantin Belousov > Date: Tue Jan 2 00:22:44 2024 +0200 > >

Re: How to upgrade an EOL FreeBSD release or how to make it working again

Judging by a commit message BSD on the ARM Chromebook didn't work when support was removed in 2019. >RK* Exynos* and Meson*/Odroid* don't even work with current >source code, if someone wants to make them work again they >better use the Linux DTS.

Re: NFSv4 crash of CURRENT

Rick, I can confirm Kostik’s fix works on 13-stable. Peter > On 15 Jan 2024, at 16:13, Peter Blok wrote: > > I can give it a shot on one of my clients. > >> On 15 Jan 2024, at 16:04, Rick Macklem > > wrote: >> >> On Mon, Jan 15, 2024 at 2:53 AM Peter Blok >

Re: NFSv4 crash of CURRENT

I can give it a shot on one of my clients. > On 15 Jan 2024, at 16:04, Rick Macklem wrote: > > On Mon, Jan 15, 2024 at 2:53 AM Peter Blok > wrote: >> >> Hi, >> >> Forgot to mention I’m on 13-stable. The fix that is causing the crash with >> automounted NFS is: >>

Re: NFSv4 crash of CURRENT

On Mon, Jan 15, 2024 at 2:53 AM Peter Blok wrote: > > Hi, > > Forgot to mention I’m on 13-stable. The fix that is causing the crash with > automounted NFS is: > > commit cc5cda1dbaa907ce52074f47264cc45b5a7d6c8b > Author: Konstantin Belousov > Date: Tue Jan 2 00:22:44 2024 +0200 > >

Re: poudriere: swap_pager: out of swap space

On Jan 15, 2024, at 00:07, Lexi Winter wrote: > Mark Millard: >> You seem to be under the impression that "Inact" means "page is not >> dirty" and so can be freed without being written out to the swap >> space. > > indeed, i was, because this is how sysutils/htop displays memory usage: > >

Re: NFSv4 crash of CURRENT

Hi, Forgot to mention I’m on 13-stable. The fix that is causing the crash with automounted NFS is: commit cc5cda1dbaa907ce52074f47264cc45b5a7d6c8b Author: Konstantin Belousov Date: Tue Jan 2 00:22:44 2024 +0200 nfsclient: limit situations when we do unlocked read-ahead by nfsiod

Re: noatime on ufs2

On Jan 15, 2024, at 01:27, Tomoaki AOKI wrote: > On Sun, 14 Jan 2024 16:13:06 -0800 > Mark Millard wrote: > >> On Jan 14, 2024, at 14:27, Tomoaki AOKI wrote: >> >>> On Sun, 14 Jan 2024 10:53:34 -0800 >>> Mark Millard wrote: >>> On Jan 14, 2024, at 08:39, Olivier Certner wrote:

Re: noatime on ufs2

On Sun, 14 Jan 2024 16:13:06 -0800 Mark Millard wrote: > On Jan 14, 2024, at 14:27, Tomoaki AOKI wrote: > > > On Sun, 14 Jan 2024 10:53:34 -0800 > > Mark Millard wrote: > > > >> On Jan 14, 2024, at 08:39, Olivier Certner wrote: > >> > >>> Hi Mark, > >>> > I never use atime, always

Re: NFSv4 crash of CURRENT

Hi, I do have a crash on a NFS client with stable of today (4c4633fdffbe8e4b6d328c2bc9bb3edacc9ab50a). It is also autofs related. Maybe it is the same problem. I have ports automounted on /am/ports. When I do cd /am/ports/sys and type tab to autocomplete it crashes with the below stack trace.

Re: poudriere: swap_pager: out of swap space

Mark Millard: > You seem to be under the impression that "Inact" means "page is not > dirty" and so can be freed without being written out to the swap > space. indeed, i was, because this is how sysutils/htop displays memory usage: top(1) Mem: 8502M Active, 15G Inact, 1568M Laundry, 5518M

Re: noatime on ufs2

Am 2024-01-15 00:08, schrieb Olivier Certner: Hi Warner, The consensus was we'd fix it in the installer. Isn't speaking about a "consensus", at least as a general response to the idea of making 'noatime' the default, a little premature? I have more to say on this topic (see below). Also,

Re: noatime on ufs2

Am Sun, 14 Jan 2024 19:14:16 +0100 schrieb "Patrick M. Hausen" : > That number at first looks like a serious load on the write endurance > of your SSD. Then, doing the math it turns out it's absolutely > ridiculous. > > 100 kB/s sums up to 8,640 GB/day (in decimal units). Even the small > SSDs

Re: NFSv4 crash of CURRENT

Am Sun, 14 Jan 2024 20:34:12 -0800 Cy Schubert schrieb: > In message om> > , Rick Macklem writes: > > On Sat, Jan 13, 2024 at 12:39=E2=80=AFPM Ronald Klop = > > wrote: > > > > > > > > > Van: FreeBSD User > > > Datum: 13 januari 2024 19:34 > > > Aan: FreeBSD CURRENT > > > Onderwerp: NFSv4

Re: NFSv4 crash of CURRENT

In message , Rick Macklem writes: > On Sat, Jan 13, 2024 at 12:39=E2=80=AFPM Ronald Klop = > wrote: > > > > > > Van: FreeBSD User > > Datum: 13 januari 2024 19:34 > > Aan: FreeBSD CURRENT > > Onderwerp: NFSv4 crash of CURRENT > > > > Hello, > > > > running CURRENT client (FreeBSD 15.0-CURRENT

Re: noatime on ufs2

On Jan 14, 2024, at 15:15, Olivier Certner wrote: > Hi Mark, > >> I seriously care about having a lack of access times. > > Then, I think elaborating on your use cases would be valuable to the > discussion, if by chance you want to and can share about them. I'm confused: I go to the trouble

Re: noatime on ufs2

On Jan 14, 2024, at 14:27, Tomoaki AOKI wrote: > On Sun, 14 Jan 2024 10:53:34 -0800 > Mark Millard wrote: > >> On Jan 14, 2024, at 08:39, Olivier Certner wrote: >> >>> Hi Mark, >>> I never use atime, always noatime, for UFS. That said, I'd never propose changing the long standing

Re: noatime on ufs2

Hi Mark, > I seriously care about having a lack of access times. Then, I think elaborating on your use cases would be valuable to the discussion, if by chance you want to and can share about them. Thanks and regards. -- Olivier Certner signature.asc Description: This is a digitally signed

Re: noatime on ufs2

Hi Warner, > The consensus was we'd fix it in the installer. Isn't speaking about a "consensus", at least as a general response to the idea of making 'noatime' the default, a little premature? I have more to say on this topic (see below). Also, I would not dismiss Lyndon's last mail too

Re: noatime on ufs2

Olivier Certner wrote: > I've mentioned your answer in another response to Lyndon Nerenberg when > developing a more general argument that 'atime' is generally flawed for these > kinds of use cases (finding the last use, finding files to backup, etc.). > It's true that the ability to

Re: noatime on ufs2

On Sun, 14 Jan 2024 10:53:34 -0800 Mark Millard wrote: > On Jan 14, 2024, at 08:39, Olivier Certner wrote: > > > Hi Mark, > > > >> I never use atime, always noatime, for UFS. That said, I'd never propose > >> changing the long standing defaults for commands and calls. > > > > With this mail,

Re: noatime on ufs2

On Jan 14, 2024, at 08:39, Olivier Certner wrote: > Hi Mark, > >> I never use atime, always noatime, for UFS. That said, I'd never propose >> changing the long standing defaults for commands and calls. > > With this mail, you're giving more detailed objections on the > social/political

Re: noatime on ufs2

Hi folks, that's a really interesting polite and constructive discussion going on here, and a trip down history lane to boot :-) I just want to add one thing to Warner's last argument: > Am 14.01.2024 um 18:58 schrieb Warner Losh : > Though in all honesty, I've never been able to measure a

Re: noatime on ufs2

Warner Losh writes: > > I'm really interested in hearing from people who actively use > > atime on a regular basis for non-trivial purposes. What are > > the modern use cases for atime? > The consensus was we'd fix it in the installer. Sure, but my question still stands. I'm genuinely curious

Re: noatime on ufs2

On Sun, Jan 14, 2024, 10:24 AM Lyndon Nerenberg (VE7TFX/VE6BBM) < lyn...@orthanc.ca> wrote: > > > I do not have a strong opinion w.r.t. atime, but I do believe that > > > changing the default would be a POLA violation. > > I'm not prepared to just accept that at face value. > > I can't think of a

Re: noatime on ufs2

> > I do not have a strong opinion w.r.t. atime, but I do believe that > > changing the default would be a POLA violation. I'm not prepared to just accept that at face value. I can't think of a single instance in at least the last three decades where I have actually used or needed atime for

Re: noatime on ufs2

Hi Mike, > I like the idea of an option in bsdinstall, but I don't think it is necessary > to check the storage type. It could simply default to noatime. > > I think we should automatically use noatime on SD card images (where > bsdinstall > doesn't get used). One of the perhaps

Re: noatime on ufs2

Hi Rodney, > ... Very well said Mark ... I don't share that enthusiasm. Please see my direct response to Mark. > Please folks stop tweaking defaults, especially long standing ones, > if you feel the need for noatime, set it, by all means, I have been > for 30 years If you're implying

Re: noatime on ufs2

Hi Mark, > I never use atime, always noatime, for UFS. That said, I'd never propose > changing the long standing defaults for commands and calls. With this mail, you're giving more detailed objections on the social/political aspects of the proposed changed, or as we usually say more simply,

Re: noatime on ufs2

Hi Rick, > I do not have a strong opinion w.r.t. atime, but I do believe that > changing the default would be a POLA violation. While I value POLA very highly, at the same time I do not consider it a sacrosanct principle that must be followed in every possible circumstances. There are many

Re: noatime on ufs2

Hi Jamie, > I've often wished there was the ability to set a process to "noatime" - where > all accesses to the filesytem by the process and its children don't alter > atime. It would be handy for those cases you describe above, such as backups > and locate, but these days, where it matters, and

<    4   5   6   7   8   9   10   11   12   13   >