On Mon, Sep 05, 2022 at 01:19:29AM +1000, David wrote:
> 6) e2fsck is capable of checking multiple filesystems at the same time, for
>faster completion when there are multiple drives with the same number in
>the 'passno' field of /etc/fstab.
>
>But, as noted by David Wright, e2fsck is
On Sun, 4 Sept 2022 at 22:15, Mike wrote:
> Thanks for the very detailed description. This was just what I was
> after. I'd kind of figured a few things, that it likely needed some
> kind of switch to fsck to produce output and likely systemd was either
> not passing that flag or swallowing the
On Sun 04 Sep 2022 at 13:15:24 (+0100), Mike wrote:
> On Sun, Sep 04, 2022 at 01:01:03AM +1000, David wrote:
> > On Sun, 4 Sept 2022 at 00:18, Charles Curley
> > wrote:
> > > On Sat, 3 Sep 2022 22:57:19 +1000 David wrote:
> >
> > > > I imagine that could be overcome by copying the above service
On Sun, Sep 04, 2022 at 01:01:03AM +1000, David wrote:
> On Sun, 4 Sept 2022 at 00:18, Charles Curley
> wrote:
> > On Sat, 3 Sep 2022 22:57:19 +1000 David wrote:
>
> > > I imagine that could be overcome by copying the above service file to
> > > /etc/lib/systemd/system/systemd-fsck-root.servic
On Sat 03 Sep 2022 at 11:31:27 (-0400), Greg Wooledge wrote:
> On Sat, Sep 03, 2022 at 10:06:56AM -0500, David Wright wrote:
> > When I booted my system this morning, I naturally selected the FSCK
> > option in Grub, and sure enough, I saw a progress bar as the root
> > filesystem was checked. Noth
On 2022-09-01 22:51 +0100, Mike wrote:
> A long time, maybe 11 years ago, I built a NAS box based around comodity
> hardware and the Debian of the day. It's currently been through several
> apt-get dist-upgrades and currently running Debian 11 with loads of old
> config grandfathered into it.
>
>
On 9/3/2022 4:18 PM, Charles Curley wrote:
On Sat, 3 Sep 2022 22:57:19 +1000
David wrote:
Nice write-up, especially the last part.
One nit-pick
I imagine that could be overcome by copying the above service file to
/etc/lib/systemd/system/systemd-fsck-root.service and editing the
above Ex
On Sat, Sep 03, 2022 at 10:06:56AM -0500, David Wright wrote:
> When I booted my system this morning, I naturally selected the FSCK
> option in Grub, and sure enough, I saw a progress bar as the root
> filesystem was checked. Nothing for the others, though. (I use
> systemd. I'm sure it's trivial t
On Sat 03 Sep 2022 at 08:18:18 (-0600), Charles Curley wrote:
> On Sat, 3 Sep 2022 22:57:19 +1000
> David wrote:
>
> Nice write-up, especially the last part.
>
> One nit-pick
>
>
> > I imagine that could be overcome by copying the above service file to
> > /etc/lib/systemd/system/systemd-fsc
On Sat 03 Sep 2022 at 08:03:38 (-0400), Greg Wooledge wrote:
> On Sat, Sep 03, 2022 at 09:56:34AM +0100, Mike wrote:
> > Rereading my original request, I think perhaps I wasn't entirely clear
> > on a couple of points:
>
> I thought it was clear. Some of the responses completely baffled me.
> One
On Sun, 4 Sept 2022 at 00:18, Charles Curley
wrote:
> On Sat, 3 Sep 2022 22:57:19 +1000 David wrote:
> > I imagine that could be overcome by copying the above service file to
> > /etc/lib/systemd/system/systemd-fsck-root.service and editing the
> > above ExecStart line to use /sbin/fsck instea
On Sat, 3 Sep 2022 22:57:19 +1000
David wrote:
Nice write-up, especially the last part.
One nit-pick
> I imagine that could be overcome by copying the above service file to
> /etc/lib/systemd/system/systemd-fsck-root.service and editing the
> above ExecStart line to use /sbin/fsck instead.
On Sat, 3 Sept 2022 at 18:57, Mike wrote:
> Thanks for the replies.
>
> Rereading my original request, I think perhaps I wasn't entirely clear
> on a couple of points:
[...]
Hi again.
Those points seemed clear to me.
> Maybe I'm being nostalgic but I seem to recall in days gone by that fsck
>
On 9/3/22 04:56, Mike wrote:
On Fri, Sep 02, 2022 at 12:31:35AM +0200, DdB wrote:
Just thinking about your request ...
Imagine this: You run "fsck -N ..." and get a rough estimate about the
time necessary to get the I/O and the job done, then it would be easy to
set up some timed countdown i
On Sat, Sep 03, 2022 at 09:56:34AM +0100, Mike wrote:
> Rereading my original request, I think perhaps I wasn't entirely clear
> on a couple of points:
I thought it was clear. Some of the responses completely baffled me.
One person even mentioned xterm -- like, *what*? How does xterm come
into p
On Fri, Sep 02, 2022 at 12:31:35AM +0200, DdB wrote:
> Just thinking about your request ...
>
> Imagine this: You run "fsck -N ..." and get a rough estimate about the
> time necessary to get the I/O and the job done, then it would be easy to
> set up some timed countdown in parallel with the real
Along the lines of what the others have said, as a policy it is always an
extremely excellent idea to make frequent and thorough backupa an store them
in two or three separate places as cloud based storage is abundant and dirt
cheap.
On September 1, 2022 6:56:16 PM PDT, David wrote:
>On Fr
On Fri, 2 Sept 2022 at 07:59, Mike wrote:
[... fsck ... it would be nice to see the progress bar ...]
> Does anyone have any suggestions for a solution or indeed where one may
> look for one?
Hi,
To add to other replies, there is information about the '-C' option of the fsck
command in two dif
On Thu 01 Sep 2022 at 22:51:44 (+0100), Mike wrote:
> It's a server, so runs 24x7 but every few months or so falls on its
> arse. Periodically it wants to fsck the disks, either because they've
> gone 20 mounts or so without a fsck or more often because they've gone
> however many days it is witho
Just thinking about your request ...
Imagine this: You run "fsck -N ..." and get a rough estimate about the
time necessary to get the I/O and the job done, then it would be easy to
set up some timed countdown in parallel with the real fsck job, just for
you to have an idea about the time left.
Al
20 matches
Mail list logo
