[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#474698: marked as done (partman-base: Inconsistent output if sector size != 512 bytes)

Your message dated Sat, 26 Apr 2008 21:18:38 -0300
with message-id <87y770xi8x.fsf@neumann.lab.ossystems.com.br>
and subject line Re: Bug#474698: partman-base: Inconsistent output if sector size != 512 bytes
has caused the Debian Bug report #474698,
regarding partman-base: Inconsistent output if sector size != 512 bytes
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

474698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474698
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: partman-base
Severity: normal

Issue the following commands in the D-I shell:

~ # modprobe raid1
~ # mdadm --create /dev/md0 --auto=yes -l1 -n2 /dev/ram0 /dev/ram1
mdadm: array /dev/md0 started.

Then restart partman.  With the text backend it says:

  6. RAID1 device #0 - 8.3 MB Software RAID device     
  7. >      #1   4.2 MB      

Note the inconsistent size report.  This is probably caused by
the ramdisks having sector size of 1024 bytes, as per:

~ # fdisk -l /dev/md0
Note: sector size is 1024 (not 512)

Disk /dev/md0: 8 MB, 8323072 bytes
2 heads, 4 sectors/track, 1016 cylinders
Units = cylinders of 8 * 1024 = 8192 bytes

As persistent storage devices can also have non 512 byte sectors,
this issue can have real impact on the installer, at least by
confusing users.


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

--- End Message ---
--- Begin Message ---
Ferenc Wagner <wferi@niif.hu> writes:

> Frans Pop <elendil@planet.nl> writes:
>> On Tuesday 22 April 2008, Ferenc Wagner wrote:
>>> Frans Pop <elendil@planet.nl> writes:
>>>>> # ~/installcd/parted/parted/parted /dev/ram1
>>>>> Error: Error opening /dev/ram1: Invalid argument
>>>>> Retry/Cancel? c
>>>> If current parted does support that correctly, I suggest you file a BR
>>>> against the experimental version of parted.
>>> Sounds like a good idea.
>>> I opened ticket #192 in the Parted Trac.
>>> http://parted.alioth.debian.org/cgi-bin/trac.cgi/ticket/192
>>> Should I duplicate it in the Debian Bug Tracker?
>> I actually meant the Debian BTS (I doubt upstream sees 1.8 as experimental), 
>> so yes, I think you should.
>> Please add the link to the upstream BR using the "Forwarded:" pseudo-header 
>> when you submit the BR, and maybe add an "upstream" tag.
> Done: #477378

This is not a bug and is being done since 2006 (1.8.0). I see the
motivation to use ramdisk for testing but it doesn't behave exactly
like a disk. Please use loopback devices for those tests.

I'm closing this bug.

        O T A V I O    S A L V A D O R
 E-mail: otavio@debian.org      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://otavio.ossystems.com.br
"Microsoft sells you Windows ... Linux gives
 you the whole house."

--- End Message ---

Reply to: