Bug 1438293 - resize2fs core dump (on shrink)
Summary: resize2fs core dump (on shrink)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: e2fsprogs
Version: 25
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Lukáš Czerner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-02 22:11 UTC by nholloway2007
Modified: 2017-12-12 10:28 UTC (History)
7 users (show)

Fixed In Version:
Clone Of: 1374494
Environment:
Last Closed: 2017-12-12 10:28:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description nholloway2007 2017-04-02 22:11:35 UTC
+++ This bug was initially created as a clone of Bug #1374494 +++

I booted from a Fedora 25 live USB in an attempt to decrypt and resize my LVM partition, and resize2fs fails with this same error. I attempted to find the core dump given the following...

"# resize2fs -p /dev/mapper/fedora-home 852g
resize2fs 1.43.1 (08-Jun-2016)
Resizing the filesystem on /dev/mapper/fedora-home to 223346688 (4k) blocks.
Begin pass 3 (max = 6980)
Scanning inode table          -------------------------------------XXXXXXXXXXXXXXXXXXXXSegmentation fault (core dumped)"

...howver, coredumpctl tells me there are no core dumps available.

Can anyone point me in the direction of a workaround or fix for this? Thanks!

Description of problem:

http://www.systutorials.com/124416/shrinking-a-ext4-file-system-on-lvm-in-linux/

# lvresize --resizefs --size SIZE /dev/vg/vg_data
this do a core dump line 141 (IIRC) in line: 
dry() {

resize2fs /dev/mapper/vg_cloud-LogVol00 75G 
also coredump 

I boot with on pen disk with Fedora 21 , and I could shrinking ext4 without problem , but the root of the problem seems shrinking with 
e2fsprogs-1.43.1-2.fc25

Version-Release number of selected component (if applicable):

Fedora 25 Alpha updated 

This is not a thing that I can test much , because I have to umount my /home partition, I decide resize my logical volumes , I wanted have more 10 Gigas in root fs  so I shrink it from /home  .
Anyway the disk in an old 80gigas matrox ,  feel free to ask more data.

--- Additional comment from Eric Sandeen on 2016-09-08 16:50:28 EDT ---

Ok, we will need more info - the core file, at least.

An e2image -Q of /dev/mapper/vg_cloud-LogVol00 should also help us reproduce the problem.

--- Additional comment from Sergio Monteiro Basto on 2016-09-10 00:48:15 EDT ---

sd 2:0:0:0: [sda] 390721968 512-byte logical blocks: (200 GB/186 GiB) 200 gigas 

hdparm -i /dev/sda

/dev/sda:

 Model=Maxtor 6L200M0, FwRev=BANC1G10, SerialNo=L41V8MNG
 Config={ Fixed }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
 BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=390721968
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4 
 DMA modes:  mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 
 AdvancedPM=yes: disabled (255) WriteCache=enabled
 Drive conforms to: ATA/ATAPI-7 T13 1532D revision 0:  ATA/ATAPI-1,2,3,4,5,6,7

 * signifies the current active mode

About e2image -Q  "using either the -r or -Q options, the filesystem must be unmounted or  be  mounted read/only" and I send you all directory data of my /home  , at least will consume many time , "However, the filenames in the directory blocks can still reveal information about the contents of the filesystem that the bug reporter may wish to keep confidential" yes , I will not send all my titles material (videos, songs etc) "To address this concern, the -s option can be specified" ok with -s and even so , I don't know .

--- Additional comment from Eric Sandeen on 2016-09-10 10:50:46 EDT ---

(In reply to Sergio Monteiro Basto from comment #2)
> sd 2:0:0:0: [sda] 390721968 512-byte logical blocks: (200 GB/186 GiB) 200
> gigas 
> 
> hdparm -i /dev/sda

hdparm is not useful.

> About e2image -Q  "using either the -r or -Q options, the filesystem must be
> unmounted or  be  mounted read/only" and I send you all directory data of my
> /home  , at least will consume many time , "However, the filenames in the
> directory blocks can still reveal information about the contents of the
> filesystem that the bug reporter may wish to keep confidential" yes , I will
> not send all my titles material (videos, songs etc) "To address this
> concern, the -s option can be specified" ok with -s and even so , I don't
> know .

Ok, I can't proceed without any further information.  If you can provide it, please re-open.

Comment 1 Sergio Basto 2017-04-19 10:29:05 UTC
Ok, we will need more info - the core file, at least.

An e2image -Q of /dev/mapper/vg_cloud-LogVol00 should also help us reproduce the problem.

Comment 2 Fedora End Of Life 2017-11-16 19:17:41 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:28:54 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.