Displaying 3 results from an estimated 3 matches for "ronnyegn".
Did you mean:
ronnen
2014 Aug 17
1
/dev/disk/by-uuid missing
...51b7-393d-4df9-9b58-f06a0a80a748
/dev/sdb3 ext4 / 8ef1f6cb-5dfc-497e-83d0-8d91cbbe4939
---8<---
Any help?
btw., the problem appeared when I installed a 18TB raid array. I had
to compile the e2fsprogs from the most recent sources using this
recipe
http://blog.ronnyegner-consulting.de/2011/08/18/ext4-and-the-16-tb-limit-now-solved
to install a very large ext4 file system on the raid disk.
best regards
---
Michael Schumacher
PAMAS Partikelmess- und Analysesysteme GmbH
Dieselstr.10, D-71277 Rutesheim
Tel +49-7152-99630
Fax +49-7152-996333
Gesch?ftsf?hrer: Gerhard...
2012 Aug 04
2
resize too large
I have a file system I am trying to resize via resize2fs but I get this error
resize2fs 1.41.14 (22-Dec-2010)
resize2fs: New size too large to be expressed in 32 bits
im on debian squeeze 2.6.32-5-amd64
# pvs
? PV???????? VG????? Fmt? Attr PSize? PFree
? /dev/md1?? vgRAID6 lvm2 a-?? 18.17t 134.12g
# lvs
? LV??? VG????? Attr?? LSize? Origin Snap%? Move Log Copy%? Convert
? data1 vgRAID6 -wi-ao
2012 Jan 22
2
Best practices?
Suppose I start building nodes with (say) 24 drives each in them.
Would the standard/recommended approach be to make each drive its own
filesystem, and export 24 separate bricks, server1:/data1 ..
server1:/data24 ? Making a distributed replicated volume between this and
another server would then have to list all 48 drives individually.
At the other extreme, I could put all 24 drives into some