Bug 158218 - confusing message/choice when sector size != 512 bytes detected
confusing message/choice when sector size != 512 bytes detected
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: parted (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Cantrell
Brock Organ
: Translation
Depends On:
Blocks: 181409
  Show dependency treegraph
Reported: 2005-05-19 13:33 EDT by David Lehman
Modified: 2013-01-10 16:42 EST (History)
6 users (show)

See Also:
Fixed In Version: RHBA-2006-0384
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-10 17:27:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
parted exception message rewording (728 bytes, patch)
2006-04-13 13:31 EDT, David Cantrell
no flags Details | Diff
updated translations for new message string (175.59 KB, patch)
2006-04-28 17:28 EDT, Paul Gampe
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2006:0384 normal SHIPPED_LIVE parted bug fix update 2006-08-09 00:00:00 EDT

  None (edit)
Description David Lehman 2005-05-19 13:33:28 EDT
Description of problem:
If you run parted on a disk whose sector size is not 512 bytes it presents a
warning as follows:

    The sector size on /dev/sdb is 4096 bytes.  Parted is known not to work
    properlywith drives with sector sizes other than 512 bytes

As it turns out, "Cancel" in this case means "pretend the disk has 512 bytes
sectors" whereas "Ignore" means "ignore the warning and proceed with 4096 byte
sectors". This is highly confusing to any who have not read the code. Most
confusing is the fact that entering "cancel" at this prompt does not cause
parted to exit.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run parted on a disk whose sector size is not 512 bytes (eg a huge SCSI disk)
2. Type "cancel" when presented with the above message
Actual results:
Parted appears to continue as though you selected "ignore". It makes no mention
before or after of the fact that you are choosing sector sizes, not whether or
not to continue at all.

Expected results:
A clear message that asks the user a) whether or not to continue at all and, if
so, b) whether to use the detected sector size or parted's default (512 bytes).

Additional info:
Comment 9 David Cantrell 2006-04-11 11:19:07 EDT
I can reword the exception handler to present a yes/no question for this
situation.  If I add text to the message, it will need to be translated to the
other languages.

I can fix this for RHEL4U4.
Comment 10 David Cantrell 2006-04-13 13:31:29 EDT
Created attachment 127716 [details]
parted exception message rewording

Here's the patch I'm proposing.  I changed it to ask a yes/no question and
added the sentence "Use NNN sector size?"
Comment 11 David Cantrell 2006-04-13 13:32:51 EDT
mkim:  Is translation for this patch possible for RHEL4U4?
Comment 12 Michelle Kim 2006-04-16 22:50:42 EDT
Sure David, 
Is it okay if I provide translation for the following particular sentence in
text format?

The sector size on %s is %d bytes.  Parted is known not to work properly with
drives with sector sizes other than %d bytes.  Use %d sector size?"

Once I gather translation from each translator, I will attach the translation
back to this ticket.

Comment 13 David Cantrell 2006-04-17 13:34:20 EDT

That will be fine.  I can add the translations to the patch for the package. 
I've committed to April 28th for early release errata for this package.  Can you
get the translations to me before then?

Comment 14 David Cantrell 2006-04-26 11:39:13 EDT
Still waiting on translations for this update.
Comment 15 Michelle Kim 2006-04-27 21:00:45 EDT
Hi David,

Thanks for waiting. Please find the attached translations for 14 supported 
langs from translation team in Brisbane:

English: The sector size on %s is %d bytes.  Parted is known not to work 
with drives with sector sizes other than %d bytes.  Use %d sector size?"

Korean: %s 상 섹터 용량은 %d 바이트입니다. Parted는 섹터 용량이 %d 바이트 보다 클 경우 
드라이브를 제대로 파티션하지 못합니다. 섹터 용량을 %d으로 하시겠습니까?

German: Die Sektorgröße auf %s ist %d Bytes.  Parted ist dafür bekannt nicht 
einwandfrei mit Laufwerken zu arbeiten, die eine Sektorgröße ungleich %d Bytes 
verwenden.  %d Bytes Sektorgröße verwenden?

Punjabi: %s ਉੱਪਰ ਸੈਕਟਰ ਅਕਾਰ %d ਬਾਈਟ ਹੈ। ਵਿਭਾਜਨ ਕੀਤੇ ਬਾਰੇ ਜਾਣਕਾਰੀ ਹੈ ਕਿ %d ਬਾਈਟ ਤੋਂ ਵੱਖਰੇ 
ਸੈਕਟਰ ਅਕਾਰ ਵਾਲੀਆਂ ਡਰਾਈਵਾਂ ਨਾਲ ਠੀਕ ਤਰਾਂ ਕੰਮ ਨਹੀਂ ਕਰਦਾ। %d ਸੈਕਟਰ ਅਕਾਰ ਵਰਤੋ?

Bengali: %s'র উপর সেক্টরের মাপ হল %d বাইট। %d বাইট ব্যাতীত অন্যান্য মাপের সেক্টরের সাথে parted 
জ্ঞানত চলতে সক্ষম নয়। পরিবর্তে %d মাপের সেক্টর প্রয়োগ করা হবে কি?

Hindi: %s पर सेक्टर आकार %d बाइट का है.  विभाजित किया हुआ %d बाइट के अलावे सेक्टर आकार के 
ड्राइव के साथ ठीक से काम करता हुआ नहीं प्रतीत होता है.  %d सेक्टर आकार का प्रयोग करें?

Gujarati: %s પરનું સેક્ટર માપ એ %d બાઈટો છે. Parted એ %d બાઈટો સિવાયના અન્ય માપ સાથેની 
ડ્રાઈવો સાથે યોગ્ય રીતે કામ નહિં કરવા માટે જાણીતું છે. શું %d સેક્ટર માપ વાપરવું છે?

Tamil: %s ன் வட்டக்கூறு அளவு %d பைட்டுகள் ஆகும். பிரிக்கப்பட்டது இயக்கிகளுடன் 
%d பைட் 
வட்டக்கூறு அளவுகளில் சரியாக பணி செய்யவில்லை. %d வட்டக்கூறு அளவினை 

Japanese: %s 上のセクターサイズは %d バイトです。Parted は %d バイト以外のセクターサイ
知られています。%d のセクターサイズを使用しますか?

French: La taille du secteur sur %s est %d octets. Parted ne fonctionne pas 
correctement avec des pilotes de taille de secteur différente de %d 
octets. Souhaitez-vous utiliser une taille de secteur de %d ?

Spanish: El tamaño de sector en %s es de %d bytes. Se sabe que Parted no 
apropiadamente con dispositivos que tienen un tamaño de sector diferente
a %d bytes. ¿Utilizar tamaño de sector de %d?

Italian: La dimensione del settore su %s è di %d byte. Parted non funziona
correttamente se utilizzato con drive con dimensioni del settore diverse
da %d byte. Utilizzare %d come dimensione del settore?

Traditional Chinese: %s 上的磁區大小是 %d 位元組。Parted 只能在磁區大小為 %d 位元組的
硬碟上運作。您要使用 %d 磁區大小嗎?

Simplified Chinese: 在 %s 上的扇区的大小是 %d 字节。Parted 无法在扇区大于 %d 字节的驱
动器上正常工作。使用大小为 %d 的扇区?

Russian: Размер сектора диска %s равен %d байт. Parted работает некорректно 
с дисками, размер секторов которых отличен от %d байт. 
Использовать размер сектора равный %d?

If you require further assitance, please let me know.

Michelle Kim

Comment 16 David Cantrell 2006-04-28 11:25:01 EDT
(In reply to comment #15)
> Hi David,
> Thanks for waiting. Please find the attached translations for 14 supported 
> langs from translation team in Brisbane:


Thanks for sending those.  I'm having trouble adding the translations to the po
files (mostly it's because I don't know how to deal with these character sets
and I'm trying various copy and paste methods from the browser).

Could you attach the translated text as a separate file that I can download?


Comment 17 Paul Gampe 2006-04-28 17:28:50 EDT
Created attachment 128378 [details]
updated translations for new message string

Dave, parted-16.19/po/ directory only has a subset of our Red Hat Tier-1
languages. That being {de,es,fr,it,ja,ru,zh_CN}.po. Please find a patch against
this language set attached.

I applied your previous patch and updated the parted.pot so you can get the
exact msgid/msgstr you are looking for. You may notice that these patches
pickup other changes you may not need so feel free to pick and choose.

I've double checked the file encodings for the patch set should be correct.
Please note that the parted .po files have not yet been converted to UTF-8
though so let me know if that causes you any problems.
Comment 18 David Cantrell 2006-05-01 11:32:19 EDT
I've added the translations and built a new package.  Thanks for the patch, Paul.
Comment 23 Red Hat Bugzilla 2006-08-10 17:27:16 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.