From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] LVM and making /var larger, file system won't resize.
Date: Sun, 11 May 2025 10:10:43 -0500 [thread overview]
Message-ID: <7910d4d3-1eff-c05e-3291-5fa66a5cf156@gmail.com> (raw)
In-Reply-To: <2981650.SvYEEZNnvj@rogueboard>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
Michael wrote:
>
> I'm not the best person to advise on LVM, I just shared what I know, but I
> haven't used LVM in anger for a few years now. Hopefully someone with more
> hands on experience will chime in.
Since the lv command worked, I don't think this is a LVM problem. That
part of the growth is there. It seems to be resize2fs that has the
problem. I just wonder, if I could do a file system check, would it
work then? Thing is, it to wants it unmounted. It makes me wonder if
there is something that needs to be fixed, even if it is minor and not a
actual data problem, but it isn't just saying the file system needs to
be fixed first. When I did my searches, most people had a part in the
output about a bad super block or that a super block wasn't found. Mine
doesn't have that tho. I'm not sure what difference that makes.
I'll try to boot some media and do it I guess. Just not today.
Dale
:-) :-)
[-- Attachment #2: Type: text/html, Size: 1560 bytes --]
next prev parent reply other threads:[~2025-05-11 15:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-11 5:41 [gentoo-user] LVM and making /var larger, file system won't resize Dale
2025-05-11 10:20 ` Michael
2025-05-11 10:40 ` Alexandru N. Barloiu
2025-05-11 12:21 ` Dale
2025-05-11 12:44 ` Michael
2025-05-11 13:10 ` Dale
2025-05-11 13:21 ` Michael
2025-05-11 14:39 ` Dale
2025-05-11 14:43 ` Michael
2025-05-11 15:10 ` Dale [this message]
2025-05-11 15:52 ` Michael
2025-05-11 16:14 ` Dale
2025-05-11 16:36 ` Jay Faulkner
2025-05-13 22:14 ` Frank Steinmetzger
2025-05-13 22:40 ` Dale
2025-05-13 22:03 ` Frank Steinmetzger
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=7910d4d3-1eff-c05e-3291-5fa66a5cf156@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.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