yashsingh1/xdaforums huggingface dataset:
[Epic 4G General] nutswillkillme:
He's back to let us know he's finished CM6, but we aren't worthy, so we can't have it.
[Epic 4G General] mykie242:
RFS, Refurbished Epic 4g from about a month ago:

FSR VERSION: FSR_1.2.1p1_b139_RTM

minor position size units id

1: 0x00000000-0x00040000 0x00040000 1 0

2: 0x00040000-0x00080000 0x00040000 1 1

3: 0x00080000-0x00a80000 0x00a00000 40 20

4: 0x00a80000-0x00bc0000 0x00140000 5 3

5: 0x00bc0000-0x00d00000 0x00140000 5 4

6: 0x00d00000-0x01200000 0x00500000 20 21

7: 0x01200000-0x01980000 0x00780000 30 6

8: 0x01980000-0x02100000 0x00780000 30 7

9: 0x02100000-0x12d80000 0x10c80000 1074 22

10: 0x12d80000-0x32f80000 0x20200000 2056 23

11: 0x32f80000-0x3de80000 0x0af00000 700 24

12: 0x3de80000-0x3eb00000 0x00c80000 50 11

(0)(0) bad mapping information

No BadUnit RsvUnit

0: 2668 4090

1: 2936 4089

2: 3706 4088

3: 4004 4087
[Epic 4G General] deano0714:
Seriously?
[Epic 4G General] steviee7:
No lol
[Epic 4G General] dreamsforgotten:
XD classic
[Epic 4G General] swear0730:
I ran this on January 5th and had 7 bad blocks. Been running EXT with each ROM and ran again today. Same 7 bad blocks.
[Epic 4G General] SINNN:
Just for the record.... I haz epic since launch date. When bad block issue came up a few months ago, I did the terminal command and it gave me 1 bad block. Ever since I have flashed daily at least twice a day. Once in the morning and later at lunch. I redid the command this evening and it came up to 1 bad block. Its safe to say this device is good quality unlike HTC POS!
[Epic 4G General] ac16313:
Possibility of having the same amount of bad blocks since purchase?

And maybe non of them were even caused by flashing?

Sent from my SPH-D700
[Epic 4G General] dreamsforgotten:
High possibility reports of 12 on a brand new device
[Epic 4G General] The Root:
I have been rooted and flashing ext4 only since March or April. 1 bad block. No idea if I already had it to begin with.
[Epic 4G General] MikeEx:
I've had the phone since November, first checked NAND and used EXT4 since feb 2.

still only 1 bad block.

I've read that you would have to have 3 bad blocks per month for 2 years for the phone to die before its life cycle.

EXT4 is perfectly safe.

EDIT: found the post with information. http://xdaforums.com/showthread.php?t=900041
[Epic 4G General] ac16313:
Hm, that doesn't seem right to sell phones like that??

Well at least that gives a indication as too ext4 not being the cause of most of them.

Sent from my SPH-D700
[Epic 4G General] SINNN:
Some poor sap here reported alot of black blocks. I forget but I think 12. No way in hell would I keep it if I could return it.
[Epic 4G General] kenvan19:
I'm going to compile the results from so far:

RFS: 0, 3, 3, 4, 5, 5, 5, 15

Average of 5 bad blocks

EXT4: 0, 0, 0, 0, 0, 1, 1, 2, 2, 3, 3, 3, 4, 7

Average of 1.64 bad blocks

I'll keep compiling as other people report but to me the only thing that really stands out are the two outliers; they both represent people who do a lot of ROM flashing. The only moral I see is to be careful how often you flash ROMs as it seems to cause a higher percentage of bad blocks.

~Updated~x9
[Epic 4G General] boctok:
Had phone since 1 November. Rooted ~ 1 December - flashed total of 3 roms, EXT4 about a week ago.

Thank you for using Better Terminal Emulator Pro

/ $ su

/ # cat /proc/L*/bmlinfo

FSR VERSION: FSR_1.2.1p1_b139_RTM

minor position size units id

1: 0x00000000-0x00040000 0x00040000 1 0

2: 0x00040000-0x00080000 0x00040000 1 1

3: 0x00080000-0x00a80000 0x00a00000 40 20

4: 0x00a80000-0x00bc0000 0x00140000 5 3

5: 0x00bc0000-0x00d00000 0x00140000 5 4

6: 0x00d00000-0x01200000 0x00500000 20 21

7: 0x01200000-0x01980000 0x00780000 30 6

8: 0x01980000-0x02100000 0x00780000 30 7

9: 0x02100000-0x12d80000 0x10c80000 1074 22

10: 0x12d80000-0x32f80000 0x20200000 2056 23

11: 0x32f80000-0x3de80000 0x0af00000 700 24

12: 0x3de80000-0x3eb00000 0x00c80000 50 11

(0)(0) bad mapping information

No BadUnit RsvUnit

0: 252 4090

1: 1023 4089

2: 2128 4088

3: 2898 4087

4: 3438 4086

/ #
[Epic 4G General] Aneirin:
$ export PATH=/data/local/bin:$PATH

$ cat /proc/L*/bmlinfo

FSR VERSION: FSR_1.2.1p1_b129_RTM

minor position size units id

1: 0x00000000-0x00040000 0x00040000 1 0

2: 0x00040000-0x00080000 0x00040000 1 1

3: 0x00080000-0x00a80000 0x00a00000 40 20

4: 0x00a80000-0x00bc0000 0x00140000 5 3

5: 0x00bc0000-0x00d00000 0x00140000 5 4

6: 0x00d00000-0x01200000 0x00500000 20 21

7: 0x01200000-0x01980000 0x00780000 30 6

8: 0x01980000-0x02100000 0x00780000 30 7

9: 0x02100000-0x12d80000 0x10c80000 1074 22

10: 0x12d80000-0x32f80000 0x20200000 2056 23

11: 0x32f80000-0x3de80000 0x0af00000 700 24

12: 0x3de80000-0x3eb00000 0x00c80000 50 11

(0)(0) bad mapping information

No BadUnit RsvUnit

0: 1886 4090

1: 3324 4089

2: 3520 4088

3: 3654 4087

4: 3996 4086

$

First there are some things people need to keep in mind. Ext4 has not been used long, and peoples usage with their hardware is a huge differentiator. These posts really provide a baseline of wear over x months of RFS for that particular user. Given continued simular usage, the question is how much wear they have over the next couple months. If wear leveling is working properly, it should be consistent with their prevous wear. To compare these posts now or compare some users against others has no meaning due to the other variables. In my case, I have had my epic since launch day and have only ever used stock. I have only rooted, no flashing.
[Epic 4G General] knyque:
I've had my Epic since the 2nd day it came out. I haven't flashed, but I am rooted. I have no bad blocks. I didn't paste it here because it's nothing new.
[Epic 4G General] adamw1101:
Doesn't the quality of flash memory vary as well?
[Epic 4G General] kenvan19:
I suppose but wouldn't it make since that since we all have the same phone bought from the same manufacturer that the quality of the flash memory would be near constant with the occasional outlier.
[Epic 4G General] chris5h:
EXT4, phone since about a month after they came it (replaced my launch day Epic for one right at the end of my 30 day window)

cat /proc/L*/bmlinfo

FSR VERSION: FSR_1.2.1p1_b139_RTM

minor position size units id

1: 0x00000000-0x00040000 0x00040000 1 0

2: 0x00040000-0x00080000 0x00040000 1 1

3: 0x00080000-0x00a80000 0x00a00000 40 20

4: 0x00a80000-0x00bc0000 0x00140000 5 3

5: 0x00bc0000-0x00d00000 0x00140000 5 4

6: 0x00d00000-0x01200000 0x00500000 20 21

7: 0x01200000-0x01980000 0x00780000 30 6

8: 0x01980000-0x02100000 0x00780000 30 7

9: 0x02100000-0x12d80000 0x10c80000 1074 22

10: 0x12d80000-0x32f80000 0x20200000 2056 23

11: 0x32f80000-0x3de80000 0x0af00000 700 24

12: 0x3de80000-0x3eb00000 0x00c80000 50 11

(0)(0) bad mapping information

No BadUnit RsvUnit

0: 2791 4090

1: 3266 4089

2: 3438 4088

3: 3830 4087
[Epic 4G General] amosher13:
Bought my Epic the day it came out: 8/31/10. Rooted several days later, flashed quite a bit in the first 3 months (almost everything possible, lol), not AS much since. Been on Quantum since 1.0 and installing every release since then, EXT4 the day it came out. Flashing here and there for testing.

Do we have any kind of baseline of what a "normal" amount of bad blocks would be per timeframe and also how many blocks have to go bad to notice any kind of impact?

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\amosher>adb shell cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11

(0)(0) bad mapping information
No BadUnit RsvUnit
0: 2802 4090
1: 3470 4089
2: 3488 4088
3: 3902 4087

C:\Documents and Settings\amosher>
[Epic 4G General] fczeuner:
Switched to EXT4 2 days ago. Epic is only 5 weeks old

$ cat /proc/L*/bmlinfo

FSR VERSION: FSR_1.2.1p1_b139_RTM

minor position size units id

1: 0x00000000-0x00040000 0x00040000 1 0

2: 0x00040000-0x00080000 0x00040000 1 1

3: 0x00080000-0x00a80000 0x00a00000 40 20

4: 0x00a80000-0x00bc0000 0x00140000 5 3

5: 0x00bc0000-0x00d00000 0x00140000 5 4

6: 0x00d00000-0x01200000 0x00500000 20 21

7: 0x01200000-0x01980000 0x00780000 30 6

8: 0x01980000-0x02100000 0x00780000 30 7

9: 0x02100000-0x12d80000 0x10c80000 1074 22

10: 0x12d80000-0x32f80000 0x20200000 2056 23

11: 0x32f80000-0x3de80000 0x0af00000 700 24

12: 0x3de80000-0x3eb00000 0x00c80000 50 11

(0)(0) bad mapping information

No BadUnit RsvUnit

0: 3430 4090

1: 3487 4089
[Epic 4G General] boctok:
Another point, since everyone started with RFS, is it not feasible that a certain number of the bad blocks were caused before the switch to EXT4?
[Epic 4G General] hydrogenwv:
Launch day Epic. Stock until DK28 leak dropped. I've flashed most of the current roms at least once. Haven't switched to RFS yet..

Not sure how to copy from the terminal, but I have 5 bad blocks.
[Epic 4G General] kenvan19:
Except that on average the number of bad blocks people on RFS has seems to be much higher than the number of bad blocks on ext 4

The person with 7 also has been flashing roms very very frequently.
[Epic 4G General] amosher13:
absolutely, i dont think thats what noob is even really trying to prove. as he said, this is just research, really this type of research will only yield REAL results over time with a lot of test cases, checking trends. but even then its quite circumstantial depending on use of the phone, flashing extent etc...
[Epic 4G General] theandrewgordon:
I have one bad block, flashed about 2 to 3 roms a week sense I got it mid September, been on ext4 since day 2 of it being available,
[Epic 4G General] sryans2004:
export PATH=/data/local/bin:$PATH

$ export PATH=/data/local/bin:$PATH

$cat /proc/L*/bmlinfo

FSR VERSION: FSR_1.2.1p1_b139_RTM

minor position size units id

1: 0x00000000-0x00040000 0x00040000 1 0

2: 0x00040000-0x00080000 0x00040000 1 1

3: 0x00080000-0x00a80000 0x00a00000 40 20

4: 0x00a80000-0x00bc0000 0x00140000 5 3

5: 0x00bc0000-0x00d00000 0x00140000 5 4

6: 0x00d00000-0x01200000 0x00500000 20 21

7: 0x01200000-0x01980000 0x00780000 30 6

8: 0x01980000-0x02100000 0x00780000 30 7

9: 0x02100000-0x12d80000 0x10c80000 1074 22

10: 0x12d80000-0x32f80000 0x20200000 2056 23

11: 0x32f80000-0x3de80000 0x0af00000 700 24

12: 0x3de80000-0x3eb00000 0x00c80000 50 11

(0)(0) bad mapping information

No BadUnit RsvUnit

0: 2988 4090

1: 2996 4089

2: 3690 4088

3: 3849 4087

Had epic since september or so, but had traded with someone else so was used. Flashed plenty of roms. Running ext4 now
[Epic 4G General] riceknight:
Unless someone just brought a phone and immediately switched to EXT4 after checking for 0 bad blocks... this test isn't going to show much unless theres a massive upswing of bad blocks for EXT4 users later on.
[Epic 4G General] musclehead84:
export PATH=/data/local/bin:$PATH

$ $cat /proc/L*/bmlinfo

FSR VERSION: FSR_1.2.1p1_b139_RTM

minor position size units id

1: 0x00000000-0x00040000 0x00040000 1 0

2: 0x00040000-0x00080000 0x00040000 1 1

3: 0x00080000-0x00a80000 0x00a00000 40 20

4: 0x00a80000-0x00bc0000 0x00140000 5 3

5: 0x00bc0000-0x00d00000 0x00140000 5 4

6: 0x00d00000-0x01200000 0x00500000 20 21

7: 0x01200000-0x01980000 0x00780000 30 6

8: 0x01980000-0x02100000 0x00780000 30 7

9: 0x02100000-0x12d80000 0x10c80000 1074 22

10: 0x12d80000-0x32f80000 0x20200000 2056 23

11: 0x32f80000-0x3de80000 0x0af00000 700 24

12: 0x3de80000-0x3eb00000 0x00c80000 50 11

(0)(0) bad mapping information

No BadUnit RsvUnit

0: 2839 4090

1: 3846 4089

$

Mine is 3 wks old running ext4 since it came out

Sent from my Evo killer!
[Epic 4G General] Dulanic:
Flash a lot. Have been using since nov. Ext4 only an hour.

export PATH=/data/local/bin:$PATH

$ $cat /proc/L*/bmlinfo

FSR VERSION: FSR_1.2.1p1_b139_RTM

minor position size units id

1: 0x00000000-0x00040000 0x00040000 1 0

2: 0x00040000-0x00080000 0x00040000 1 1

3: 0x00080000-0x00a80000 0x00a00000 40 20

4: 0x00a80000-0x00bc0000 0x00140000 5 3

5: 0x00bc0000-0x00d00000 0x00140000 5 4

6: 0x00d00000-0x01200000 0x00500000 20 21

7: 0x01200000-0x01980000 0x00780000 30 6

8: 0x01980000-0x02100000 0x00780000 30 7

9: 0x02100000-0x12d80000 0x10c80000 1074 22

10: 0x12d80000-0x32f80000 0x20200000 2056 23

11: 0x32f80000-0x3de80000 0x0af00000 700 24

12: 0x3de80000-0x3eb00000 0x00c80000 50 11

(0)(0) bad mapping information

No BadUnit RsvUnit

0: 3764 4089

1: 4006 4088

$
[Epic 4G General] spoatacus:
Got Epic on October 15th. Been running EXT4 since Jan 1.

FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11

(0)(0) bad mapping information
No BadUnit RsvUnit
0: 55 4090
1: 1490 4089
2: 1648 4088
3: 3658 4087
4: 3698 4086
5: 3706 4085
[Epic 4G General] dreamsforgotten:
Had Epic since release no ext 4 loads of flashing

cat /proc/L*/bmlinfoR VERSION: FSR_1.2.1p1_b129_RTM

nor position size units id

1: 0x00000000-0x00040000 0x00040000 1 0

2: 0x00040000-0x00080000 0x00040000 1 1

3: 0x00080000-0x00a80000 0x00a00000 40 20

4: 0x00a80000-0x00bc0000 0x00140000 5 3

5: 0x00bc0000-0x00d00000 0x00140000 5 4

6: 0x00d00000-0x01200000 0x00500000 20 21

7: 0x01200000-0x01980000 0x00780000 30 6

8: 0x01980000-0x02100000 0x00780000 30 7

9: 0x02100000-0x12d80000 0x10c80000 1074 22

10: 0x12d80000-0x32f80000 0x20200000 2056 23

11: 0x32f80000-0x3de80000 0x0af00000 700 24

12: 0x3de80000-0x3eb00000 0x00c80000 50 11

)(0) bad mapping information

No BadUnit RsvUnit

0: 1103 4090

1: 2249 4089

2: 2858 4088

3: 2861 4087

4: 3256 4086

5: 3948 4085
[Epic 4G General] bwest411:
Not sure if it matters this epic is about 3 weeks old its a refurb and I've Flashed about 3 roms and used odin once I have 2 bad blocks and iam on rfs
[Epic 4G General] DiGi760:
3 bad blocks for me on ext4.

I flashed a number of times since about the end of October on RFS. I have only flashed about 4 times on ext4. Been running ext4 since the 1.3 zip came out.
[Epic 4G General] danweb66:
I am going to ask a question now just so I can see what others think I am not flaming just trying to get a better understanding. So here it is... with these numbers regardles of the ext 4 only being out 4 days, if ext4 was going to ruin our phones or badly damage them in a few months would'nt you see a big spike in numbers. I guess my point is if we are looking at somthing that is going to take months even years to see a noticeble difference then what's the point why not use the faster working system?
[Epic 4G General] kenvan19:
Thats been the point I've taken from all of the industry professionals posts. My understanding of what they've been saying is that any harm that could be done wouldn't be evident for quite some time so why not just make our phones as fast as they can be?
[Epic 4G General] vitreoush:
My count

uh oh, 10 bad blocks for me. I hope those reserve blocks dont run out too fast. oh, been on ext4 for about oh 5 days now. don't flash too often. only used odin once when dk28 came out (but did have a failed flash at that time). wonder if how recently odin was used correlates with bad blocks. Mine was approx december 10th.
[Epic 4G General] pyroswithoutfire:
I have only one bad block and flashed to ext4 this morning. I have odined maybe three times since I got the phone in September. I tend to just root my phone and leave it at stock for the most part. Will update again in a few days to see if I have any more bad blocks.
[Epic 4G General] h2g2:
FYI to all, some number of bad blocks is perfectly fine. NAND chips don't come off the fab line perfect, there are always going to be some number of imperfections. When these chips are designed, some amount of redundant circuitry is built in to the design so that a small number of errors won't result in significantly lower yields off the wafer.

Think of it as the flash equivalent of the spare sector pool on spinning magnetic hard drives.

I don't know if Samsung does it for OneNAND but sometimes chipmakers will also engage in a process called binning. Suppose you made a batch of 1GB chips and a few of the chips had too many fabrication errors - if they were built with a modular design that allows it, you can harvest these chips, reduce the capacity and sell them as 512MB chips. GPU makers, for example, use this process to sell two or more different chips that are essentially the same design but differ in the number of SPs and clock speed.

If the goal is to assess the "damage" that a particular filesystem is going to cause, what you need to do is to measure these bad blocks over time. But a one time test isn't useful because the number of bad blocks was very likely non-zero when the phone was brand new.
[Epic 4G General] ajmcedar:
Here is mine, been running ext4 since late Sunday, 01/02/11.

Epic has been in my hand since Oct 01, 2010. Flashed a handful of times, Now on Mammons 1.1.3 with ext4 and his no journaling mod.
[Epic 4G General] kalico17:
running rfs currently

was on ext4 for 3days

if you plan on compiling

you might wanna get some people to test ext4 for a few days. comparing notes before the flash and at the end of the test

compiling now wont show any real results

export PATH=/data/local/bin:$PATH

$ export PATH=/data/local/bin:$PATH

$su

# cat/proc/L*/bmlinfo

cat/proc/L*/bmlinfo: not found

# cat /proc/L*/bmlinfo

FSR VERSION: FSR_1.2.1p1_b139_RTM

minor position size units id

1: 0x00000000-0x00040000 0x00040000 1 0

2: 0x00040000-0x00080000 0x00040000 1 1

3: 0x00080000-0x00a80000 0x00a00000 40 20

4: 0x00a80000-0x00bc0000 0x00140000 5 3

5: 0x00bc0000-0x00d00000 0x00140000 5 4

6: 0x00d00000-0x01200000 0x00500000 20 21

7: 0x01200000-0x01980000 0x00780000 30 6

8: 0x01980000-0x02100000 0x00780000 30 7

9: 0x02100000-0x12d80000 0x10c80000 1074 22

10: 0x12d80000-0x32f80000 0x20200000 2056 23

11: 0x32f80000-0x3de80000 0x0af00000 700 24

12: 0x3de80000-0x3eb00000 0x00c80000 50 11

(0)(0) bad mapping information

No BadUnit RsvUnit

0: 1023 4090

1: 1240 4089

2: 3530 4088

3: 3580 4087

had my epic since launch... i flash new roms constantly tho.. i think ive gone maybe a week tops on the same rom since i got the phone..

been flashing cm updates since cm6 pre beta 9 an when BT was dropping Viper updates almost daily, i was doing the same :/
[Epic 4G General] MadDucker:
Had since mid november. Odin at least 20 times. Flashed roms 10. Restored nandroid 5~7. Ext4 6 days.

export PATH=/data/local/bin:$PATH

$ $cat /proc/L*/bmlinfo

FSR VERSION: FSR_1.2.1p1_b139_RTM

minor position size units id

1: 0x00000000-0x00040000 0x00040000 1 0

2: 0x00040000-0x00080000 0x00040000 1 1

3: 0x00080000-0x00a80000 0x00a00000 40 20

4: 0x00a80000-0x00bc0000 0x00140000 5 3

5: 0x00bc0000-0x00d00000 0x00140000 5 4

6: 0x00d00000-0x01200000 0x00500000 20 21

7: 0x01200000-0x01980000 0x00780000 30 6

8: 0x01980000-0x02100000 0x00780000 30 7

9: 0x02100000-0x12d80000 0x10c80000 1074 22

10: 0x12d80000-0x32f80000 0x20200000 2056 23

11: 0x32f80000-0x3de80000 0x0af00000 700 24

12: 0x3de80000-0x3eb00000 0x00c80000 50 11

(0)(0) bad mapping information

No BadUnit RsvUnit

0: 577 4090

1: 2952 4089

2: 3514 4088

$
[Epic 4G General] kenvan19:
So what would be an unacceptable number of damaged blocks?
[Epic 4G General] jbadboy2007:
With these results so far does that not prove that ext 4 is actually better than rfs or am i just crazyyyyyyyyy :D
[Epic 4G General] hydrogenwv:
jbadboy - No, it doesn't.

The problem is all the 0s on EXT4. Since EXT4 has been out for such a short period, people spent most of the time on RFS. Which means, throughout all the time they used RFS, there were no bad blocks created.

To truly be able to analyze this, we need to know when the device was purchased, how many times they've flashed (if that REALLY is a huge issue??), and we'll have to watch for changes over time. A prospective study, for all intents and purposes. And, even then, we have different usage patterns and, as h2g2 pointed out, the chips aren't perfect from the beginning. Lots of things to consider.

Basically, looking at just means isn't really helpful since the EXT4 numbers are 'tainted' from using RFS for so long.
[Epic 4G General] MysteryEmotionz:
I flash everything already once. I do alot of flashing of my theme before I even release it. My phone is from launch. I had ext4 once released.

$ export PATH=/data/local/bin:$PATH:.

$su#cat /proc/L*/bmlinfo

FSR VERSION: FSR_1.2.1p1_b139_RTM

minor position size units id

1: 0x00000000-0x00040000 0x00040000 1 0

2: 0x00040000-0x00080000 0x00040000 1 1

3: 0x00080000-0x00a80000 0x00a00000 40 20

4: 0x00a80000-0x00bc0000 0x00140000 5 3

5: 0x00bc0000-0x00d00000 0x00140000 5 4

6: 0x00d00000-0x01200000 0x00500000 20 21

7: 0x01200000-0x01980000 0x00780000 30 6

8: 0x01980000-0x02100000 0x00780000 30 7

9: 0x02100000-0x12d80000 0x10c80000 1074 22

10: 0x12d80000-0x32f80000 0x20200000 2056 23

11: 0x32f80000-0x3de80000 0x0af00000 700 24

12: 0x3de80000-0x3eb00000 0x00c80000 50 11

(0)(0) bad mapping information

No BadUnit RsvUnit

0: 908 4090

1: 2306 4089

2: 3624 4088

#
[Epic 4G General] Toast95135:
I've had my Epic since launch day, I went to Dk28 when it first came out and flashed my first rom maybe 2 weeks ago. Ext4 has been on 6~days.

$cat /proc/L*/bmlinfo

FSR VERSION: FSR_1.2.1p1_b139_RTM

minor position size units id

1: 0x00000000-0x00040000 0x00040000 1 0

2: 0x00040000-0x00080000 0x00040000 1 1

3: 0x00080000-0x00a80000 0x00a00000 40 20

4: 0x00a80000-0x00bc0000 0x00140000 5 3

5: 0x00bc0000-0x00d00000 0x00140000 5 4

6: 0x00d00000-0x01200000 0x00500000 20 21

7: 0x01200000-0x01980000 0x00780000 30 6

8: 0x01980000-0x02100000 0x00780000 30 7

9: 0x02100000-0x12d80000 0x10c80000 1074 22

10: 0x12d80000-0x32f80000 0x20200000 2056 23

11: 0x32f80000-0x3de80000 0x0af00000 700 24

12: 0x3de80000-0x3eb00000 0x00c80000 50 11

(0)(0) bad mapping information

No BadUnit RsvUnit

0: 259 4090

1: 310 4089

2: 1269 4088

3: 2637 4087

4: 2767 4086

5: 2885 4085

6: 3995 4084

I didn't check before ext4
[Epic 4G General] nubsors:
export PATH=/data/local/bin:$PATH

$ $cat /proc/L*/bmlinfo

FSR VERSION: FSR_1.2.1p1_b139_RTM

minor position size units id

1: 0x00000000-0x00040000 0x00040000 1 0

2: 0x00040000-0x00080000 0x00040000 1 1

3: 0x00080000-0x00a80000 0x00a00000 40 20

4: 0x00a80000-0x00bc0000 0x00140000 5 3

5: 0x00bc0000-0x00d00000 0x00140000 5 4

6: 0x00d00000-0x01200000 0x00500000 20 21

7: 0x01200000-0x01980000 0x00780000 30 6

8: 0x01980000-0x02100000 0x00780000 30 7

9: 0x02100000-0x12d80000 0x10c80000 1074 22

10: 0x12d80000-0x32f80000 0x20200000 2056 23

11: 0x32f80000-0x3de80000 0x0af00000 700 24

12: 0x3de80000-0x3eb00000 0x00c80000 50 11

(0)(0) bad mapping information

No BadUnit RsvUnit

0: 1218 4089

1: 2282 4088

2: 2644 4087

$

Currently running Nebula 1.0.6, EXT4. Have had it since Sunday night.

Purchased my phone back in October. Have flashed a number of roms including Cyanogen pre-betas, bonsai, DK28.