With JBD created directories not getting full disk capacity

[GoogleCodeExporter]

When i create with the wizard a jbd with 2x1,5TB seagte harddisks and share the 
created md0 mounting point via samba i see only 701 gb. 
Alt-F displays the correct 2,7TB in "Filesystems". 
When i make one big partition on each disk and share it via samba then i see 
the 2x1,3TB. In "Disk Partitioner" i get this message "cat: can't open 
'/sys/block//dev/sdb/size': No such file or directory".
There is also under free disk space this number "-1100.048".
I can also not loggin via telent and ssh (tried on windows and linux) because i 
get this "# COLUMNS=80;LINES=24;export COLUMNS LINES;".

I use an DNS-323 rev A1. It is the Alt-F 0.1B6+ from experimental flashed on 
the box.

Original issue reported on code.google.com by thxw...@gmail.com on 30 Jan 2011 at 5:19

Attachments:

• dns323.txt

[GoogleCodeExporter]

> When i create with the wizard a jbd with 2x1,5TB seagte harddisks and share 
the created md0 mounting point via samba i see only 701 gb. 
Alt-F displays the correct 2,7TB in "Filesystems". 
When i make one big partition on each disk and share it via samba then i see 
the 2x1,3TB. 

So it seems to be a "large file support" (>2GB) problem in samba

And as a matter of fact, erroneously samba configure spits:

  configure:30508: checking if large file support can be enabled
  ...
  configure:30538: result: no

I will look at this. Thanks

>In "Disk Partitioner" i get this message "cat: can't open 
'/sys/block//dev/sdb/size': No such file or directory"

I think that this problem is now fixed in svn

>I can also not loggin via telent and ssh (tried on windows and linux) because 
i get this "# COLUMNS=80;LINES=24;export COLUMNS LINES;".

This is normal. Have you tried to type some command, like

   ls -l /

and see the output?

Thanks.

PS-Please try to report only one problem per issue entry.

Original comment by whoami.j...@gmail.com on 30 Jan 2011 at 7:28

• Changed state: Accepted

[GoogleCodeExporter]

thanks for looking into it.

the command for telnet works also! 

Original comment by thxw...@gmail.com on 30 Jan 2011 at 9:00

[GoogleCodeExporter]

Added "-force have_longlong_support", should solve issue for 0.1B7.
Can't confirm, as I don't have such big disks.

Original comment by whoami.j...@gmail.com on 24 Mar 2011 at 4:01

• Changed state: Started

[GoogleCodeExporter]

Can you please verify if Alt-F issue-30 was solved with 0.1B7?
http://code.google.com/p/alt-f/issues/detail?id=30

Thanks

Original comment by whoami.j...@gmail.com on 2 Apr 2011 at 12:16

[GoogleCodeExporter]

With the new firmware the problem is solved. One minor cosmetic problem is
that the two 1.5 TB harddisks only get displayed as
500 MB. This is in the "status" and "filesystem maintenance" tab.

Thanks for the good work!

Original comment by thxw...@gmail.com on 5 Apr 2011 at 9:29

[GoogleCodeExporter]

Thanks. Set as fixed.

In relation to the second issue, i can correctly see a 1TB disk in the status 
and filesystem maintenance pages.

The disk capacity is read using the following command, in case you want to try 
it (you have to telnet/ssh the box)

  awk '{printf "%.1f GB", $0 * 512 / 1e9}' /sys/block/sda/size

It should also appear if you execute the command:

  cat /etc/bay

Are those correct?
Thanks again

Original comment by whoami.j...@gmail.com on 5 Apr 2011 at 5:00

• Changed state: Fixed

[GoogleCodeExporter]

With the commands you wrote the size is correct displayed.
 I mean in the "Filesystem Maintenance" tab. In my case, sda4 and sdb4, and
there are only 486.2 MB displayed for each.
Maybe I am wrong, but shouldn�t here displayed the full disk capacity? And
also in the status tab?

Original comment by thxw...@gmail.com on 5 Apr 2011 at 6:39

[GoogleCodeExporter]

> I mean in the "Filesystem Maintenance" tab. In my case, sda4 and sdb4, and
> there are only 486.2 MB displayed for each.
> Maybe I am wrong, but shouldn't here displayed the full disk capacity?

In the "Filesystem Maintenance" web page you see the capacity of each partition 
or filesystem on the disk, such as sda1, sda2, md0, md1... you don't see 
devices such as sda or sdb.

The disk capacity (sda, sbd...) only shows-up in the Status Page, Disk 
Utilities page, Disk Partitioner, Disk Wizard...

E.g. in this moment I have three disks, sda, sdb and sdc. In the Status Page I 
see

Bay     Dev.    Model           Capacity    
right   sda     WDC WD800JD-00MSA1  80.0 GB
left    sdb     HDS728080PLA380     82.3 GB
usb     sdc     SAMSUNG HD103UJ     1000.2 GB

Disks sda has four partitions, sda1, sda2, sda3, sda4 and the same for the sdb 
disk. Partition sda3 from disk sda and partition sdb3 from disk sdb makeup a 
raid1 array named md0, partitions sda4 and sdb4 makeup a raid0 array named md1. 
This is what I see in the RAID page:

Dev.    Capacity    Level   Components  
md0     18.6 GB     raid1   sda3 sdb3                   
md1     35.4 GB     raid0   sda4 sdb4

On top of the RAID device md0 and md1 an ext4 filesystem was created, while 
partitions sda2 from disk sda is a "normal" partition, as is sdb2, and on each 
of them an ext3 filesystem was created. This is what I see in the Filesystem 
Maintenence page:

Dev.    Size    FS  
md0     18.3GB  ext4                
md1     34.8GB  ext4                    
sda2    36.7GB  ext3                    
sdb2    36.7GB  ext3                    
sdc2    915.9GB ext3                    
sdc4    486.2MB ext3

Only partitions, sda2, or raid devices, md0, can have a filesystem on them, and 
you can only put data on a filesystem.

I don't know your level of knowledge, hope this explanation is OK for you.

Original comment by whoami.j...@gmail.com on 6 Apr 2011 at 2:30