From nobody Tue Mar 19 00:36:03 2024 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TzCT16tRGz5FLdN for ; Tue, 19 Mar 2024 00:36:21 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yw1-x1129.google.com (mail-yw1-x1129.google.com [IPv6:2607:f8b0:4864:20::1129]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TzCT158MPz4nBX for ; Tue, 19 Mar 2024 00:36:21 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-x1129.google.com with SMTP id 00721157ae682-60a0579a968so53797747b3.3 for ; Mon, 18 Mar 2024 17:36:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710808580; x=1711413380; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=sselGQQ523pgv6dubV59Hluy6q8n6MyTQS5SP8xAc2c=; b=IuTFxocOdlNDLfzOHSAdzwnk0FTz6hM8gRE8VJzxF3nX2vI1hFr+Mzcy1Kpkk1/m+f LramnSLt20/FYmLZOuOYMGQ0SpWBF+URGbPo8h1fCJKdaBbOf803sWGhhq7FyXMAaqBQ f293SdtA42C21p8DnHirZ5aHpbyeuTeZFp9Rw6FNP5R24qujj5QCtFEgjTKt3zWUwO5D nuVka5ykVZWvgfqEpbV6+fOafNUFRBSLHFUnTBhTWI3G2p6pE8oQfH8DHvvt8C3sSOpE P3Lm9+5qHnwKbkto0Hv7juri11PnNjLk5GQfBdxm0btTdxMRLwkzeQJ6KLKZjSMyKwgJ vpQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710808580; x=1711413380; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=sselGQQ523pgv6dubV59Hluy6q8n6MyTQS5SP8xAc2c=; b=l8mYgyzZW+JgPqxWFtu//oDFe/6fpg8UIzNKMHeRpL4p8fa9i8Jl3vfNLCjkmL40t4 HXwOzxU+NZJMN9MbB/hnuDOel9M00R81qAMIy7hVPehHd+T9ULbRyL4bMuMFmOQglfyj N4NFr7yXbUJKFLFd5bF2RlSVIo6EN5QdkfcxTOnCIbb7DMTJcZesOUzeFY8S/C3Yjps7 Iwqoud96SnjWUYcqShgY3OhfsEEenkXOM0+q2xuENGJ0LfkA5R6y2JC1jcen7VQl+QbG Dl8RTJ9tiecIiSAfkjicArbBsYsyqS0Vk4AWK5h94hjROzts1T24a0y6aXCoztmV3oyH 64vw== X-Gm-Message-State: AOJu0YymuzJar9Q6l2z08CBg4WBwRfFc+tKZbjgVAai++63tgvODxtV5 frOGVnmAgxKFxU+Ntpe6bk5LiN5vqarp4nyL8UilyZS1NQo/IR81V0PiW5Dtr9X/Qbfw/eQDpOn FciSdpwgS64ZKYcQn8KBLEIMq1BU= X-Google-Smtp-Source: AGHT+IET7HFY1o12qD/eMoJT9UsFakNcomzCwWRlK2lAhHpcl6qv9o2RBjqdCWgrRQryHeUPfdbZkEVkbCmiRYPxIOM= X-Received: by 2002:a25:d60b:0:b0:dc2:2799:981a with SMTP id n11-20020a25d60b000000b00dc22799981amr9374872ybg.18.1710808580107; Mon, 18 Mar 2024 17:36:20 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Kevin Oberman Date: Mon, 18 Mar 2024 17:36:03 -0700 Message-ID: Subject: Re: reboot forcing a fsck To: Jim Pazarena Cc: freebsd-questions@freebsd.org Content-Type: multipart/alternative; boundary="000000000000b23acb0613f8a93f" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4TzCT158MPz4nBX --000000000000b23acb0613f8a93f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Mar 18, 2024 at 2:08=E2=80=AFPM Jim Pazarena wrote: > I have a server which seems to have a fs issue for my exim folder. > an "ls -l" hangs. anything going near the exim folder hangs - for > whatever reason. > > If I trigger a 'reboot', I assume the boot process will automatically > enter a fsck as per the documentation. > > What is unclear is if the system will eventually g et to multi-user > mode, or hang at a CLI question from the fsck? > > I have no hands or eyes available to be there. This is a bare metal > chassis not a vm. > > Would appreciate learning the procedure which fsck uses during a boot. > (beyond what the man fsck advises) which seems to exclude this question. > > Thanks > > > -- > Jim Pazarena fquest@paz.bz > Haida Gwaii - British Columbia - Canad Booting the system will check that the root is marked CLEAN. If it is not CLEAN, and it should not be in the case you describe, it will attempt an fsck. If the fsck finds a problem, it will prompt you to select a shell. 'ENTER' runs the default, sh. You can try something like 'fsck -y VOLUME'', but it really depends on the file system settings. You can print these with 'tunefs -p VOLUME'. If journaling is enabled, you should run an 'fsck -f VOLUME' to perform a full fsck on the volume, ignoring the journal. Assuming journaling is enabled, which is default, the journal may be bad, so only an fsck -f can repair hte file system. --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000b23acb0613f8a93f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Mar 18, 2024 at 2:08=E2= =80=AFPM Jim Pazarena <fquest@paz.bz> wrote:
I have a server which seems to have a fs issue fo= r my exim folder.
an "ls -l" hangs. anything going near the exim folder hangs - for=
whatever reason.

If I trigger a 'reboot', I assume the boot process will automatical= ly
enter a fsck as per the documentation.

What is unclear is if the system will eventually g et to multi-user
mode, or hang at a CLI question from the fsck?

I have no hands or eyes available to be there. This is a bare metal
chassis not a vm.

Would appreciate learning the procedure which fsck uses during a boot.
(beyond what the man fsck advises) which seems to exclude this question.
Thanks


--
Jim Pazarena=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0fquest@paz.bz
Haida Gwaii - British Columbia - Canad

Booting the system=C2=A0 will check that the root is marked CLEAN. If it i= s not CLEAN, and it should not be in the case you describe, it will attempt= an fsck. If the fsck finds a problem, it will prompt you to select a shell= . 'ENTER' runs the default, sh.

= You can try something like 'fsck -y VOLUME'', but it really dep= ends on the file system settings. You can print these with 'tunefs -p V= OLUME'. If journaling is enabled, you should run an 'fsck -f VOLUME= ' to perform a full fsck on the volume, ignoring the journal. Assuming = journaling is enabled, which is default, the journal may be bad, so only an= fsck -f can repair hte file system.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E= -mail: rkoberman@g= mail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39E= F1B055683
--000000000000b23acb0613f8a93f--