Bug 7059
| Summary: | attaching disk image to loop doesn't make it perform partition check | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Grzegorz jaskiewicz (gj) |
| Component: | Other | Assignee: | drivers_other |
| Status: | REJECTED INVALID | ||
| Severity: | normal | CC: | protasnb |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | Linux puppet 2.6.17.10 #1 SMP Wed Aug 23 16:35:49 CEST 2006 i686 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
This is a feature request, but we don't have way yet to track those. Have you tried proposing this on LKML? |
Most recent kernel where this bug did not occur: Distribution: debian unstable Hardware Environment: x86 pM Software Environment: gnu Problem Description and Steps to reproduce: let's say that I made image of HDD for backup: dd if=/dev/sdd of=/spool/sdd-backup losetup /dev/loop0 /spool/sdd-backup fdisk -l /dev/loop0 Disk /dev/loop0: 536 MB, 536870912 bytes 32 heads, 63 sectors/track, 520 cylinders Units = cylinders of 2016 * 512 = 1032192 bytes Device Boot Start End Blocks Id System /dev/loop0p1 * 1 520 524128+ 6 FAT16 now, all nice - but there's no device called /dev/loop0p1 so I can't mount it! I wish kernel somehow scan that loop device, just like it does when I insert any sort of device, whether that's usb stick or removable drive. thank you!