|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ View Advanced ]
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Reproducibility |
Date Submitted |
Last Update |
|
0000102 |
[BusyBox] Standards Compliance |
minor |
always |
02-14-05 08:11 |
08-25-07 11:32 |
|
|
Reporter |
pking |
View Status |
public |
|
|
Assigned To |
BusyBox |
|
Priority |
normal |
Resolution |
unable to reproduce |
|
|
Status |
closed |
|
Product Version |
1.00 |
|
|
Summary |
0000102: problem with large fdisk partitions |
|
Description |
System: Familiar Linux 0.8.1 snapshot, running on an iPAQ 3955.
Running Busybox's fdisk on a 1GB SD card creates a valid partition table, but putting a filesystem > 256MB on any partition results in Busybox's fdisk being unable to read the partition table (tested for ext2, ext3, reiserfs). Likwise, if the card is formatted on a desktop with regular GNU fdisk, Busybox's fdisk can't read the partition table, which shows up fine in GNU fdisk. The upshot is that the partitions with filesystems can't be mounted via Busybox. Any partitions created that are < 256MB are automounted and work normally, although df -h gives incorrect information. |
|
Additional Information |
The desktop testing system uses a SanDisk ImageMate reader/writer, and runs Debian "sarge" release.
The exact size threshold may not be correct: I didn't try to pin down where the change occurs, but I had difficulties with partitions of 1GB, 750MB, and 640MB,
so it's possible the threshold is at 512MB. |
|
|
Attached Files |
|
|
|