Bug 1374494

Summary:	resize2fs core dump (on shrink)
Product:	[Fedora] Fedora	Reporter:	Sergio Basto <sergio>
Component:	e2fsprogs	Assignee:	Eric Sandeen <esandeen>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	esandeen, josef, kzak, oliver, sergio
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1438293 (view as bug list)		Environment:
Last Closed:	2016-09-10 14:50:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Sergio Basto 2016-09-08 20:18:08 UTC

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.

Comment 1 Eric Sandeen 2016-09-08 20:50:28 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 Sergio Basto 2016-09-10 04:48:15 UTC

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 .

Comment 3 Eric Sandeen 2016-09-10 14:50:46 UTC

(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.