From: Ram Ramesh <rramesh2400@gmail.com>
To: Wols Lists <antlists@youngman.org.uk>,
Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: My MD is too big to resize ext4.
Date: Sat, 8 Jul 2017 13:28:41 -0500 [thread overview]
Message-ID: <22e55143-b62e-edab-f621-0efac161e2c4@gmail.com> (raw)
In-Reply-To: <5960981C.9040906@youngman.org.uk>
On 07/08/2017 03:30 AM, Wols Lists wrote:resize2fs is bleeding edge? I
suspect it's v0.99 quality, ie nobody has
> the nerve to upgrade it to v1, despite it being rock solid. I know I've
> used it without trouble. Most of these utilities are pretty solid
> (unless the underlying filesystem itself is experimental ...)
>
> Cheers,
> Wol
>
The web solution talks about not yet released resize2fs source and
compiling in latest kernel etc. That is bleeding edge to me. I like to
stick to stable versions of distro.
My days of young and adventurous are gone. I have been with Linus/linux
when he released some mock alpha kernlel that would only print A/B to
show context switching. I remember the lengthy conversation/argument
that he had with Prof. Tannenbaum (sp?) on monolithic vs. micro kernel.
I enjoyed compiling kernel and reading code to figure out why some thing
did not work. However that is a long time ago. I just have aged, become
less current and rusty with tricks. I use stable distros and stick the
trusted kernel/packages in them now. So, in that context, would you not
say resize2fs approach is bleeding edge :-)
Ramesh
next prev parent reply other threads:[~2017-07-08 18:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 0:41 My MD is too big to resize ext4 Ram Ramesh
2017-07-08 6:50 ` Andreas Klauer
2017-07-08 18:12 ` Ram Ramesh
2017-07-08 19:44 ` Andreas Klauer
2017-07-08 22:22 ` Ram Ramesh
2017-07-09 23:09 ` Ram Ramesh
2017-07-08 7:34 ` Brad Campbell
2017-07-08 7:40 ` Reindl Harald
2017-07-08 8:12 ` Brad Campbell
2017-07-08 18:19 ` Ram Ramesh
2017-07-08 18:48 ` Ram Ramesh
2017-07-08 8:30 ` Wols Lists
2017-07-08 18:28 ` Ram Ramesh [this message]
2017-07-08 11:15 ` Roman Mamedov
2017-07-08 18:37 ` Ram Ramesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22e55143-b62e-edab-f621-0efac161e2c4@gmail.com \
--to=rramesh2400@gmail.com \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).