Moiunt failed. "File too Large"

Duamer · 11. Februar 2018

Error message:

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mount -v --source '/dev/dm-0' 2>&1' with exit code '32': mount: mount /dev/mapper/store-public on /srv/dev-disk-by-label-Venezia failed: File too large

Details:

Code

Error #0: exception 'OMV\ExecException' with message 'Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mount -v --source '/dev/dm-0' 2>&1' with exit code '32': mount: mount /dev/mapper/store-public on /srv/dev-disk-by-label-Venezia failed: File too large' in /usr/share/php/openmediavault/system/process.inc:175 
Stack trace: 
#0 /usr/share/php/openmediavault/system/filesystem/filesystem.inc(720): OMV\System\Process->execute() 
#1 /usr/share/openmediavault/engined/module/fstab.inc(72): OMV\System\Filesystem\Filesystem->mount() 
#2 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleFsTab->startService() 
#3 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array) 
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array) 
#5 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array) 
#6 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(857): OMV\Rpc\Rpc::call('Config', 'applyChanges', Array, Array) 
#7 [internal function]: OMVRpcServiceFileSystemMgmt->mount(Array, Array) 
#8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array) 
#9 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('mount', Array, Array) 
#10 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('FileSystemMgmt', 'mount', Array, Array, 1) 
#11 {main}

Alles anzeigen

Just got a Helios4 in the mail and spent the last two days making the RAID array. It's four 8TB drive in a RAID5 array, 21TB. Following Kobol's OMV directions, I installed the LVM plugin and created the physical volume, the volume group, and the logical volumes. I then created the file system, but when I try to mount it for the first time, I get the "File too large" error. If I backup a few steps and create two half sized logical volumes, I can successfully mount.

How can I get it to mount a 21TB volume?

tkaiser · 11. Februar 2018

https://serverfault.com/a/536758

henfri · 11. Februar 2018

If one of your drives ever fails, all data is lost.
And a drive *will* fail. The only question is 'when'.

So: Why do you want to create a raid?
I suppose you want to combine the drives to one virtual large drive. For this I would recommend mergerfs. If one drive fails with mergerfs, you only lose the data on this drive.

Apart from that, you should have a backup strategy.

By the way: A real life example from my server:

Code

snapraid smart
SnapRAID SMART report:


Temp  Power   Error   FP Size
C OnDays   Count        TB  Serial            Device    Disk
-----------------------------------------------------------------------
29    919       0  16%  3.0  35ELXMLGS         /dev/sdd  Big1_Data
35    472       -  SSD  0.1  50026B72690068A9  /dev/sdf  Big2_Data
29    986       0  13%  3.0  Z4D1MB4KS         /dev/sde  Big3_Data
21    247       0   6%  5.0  W4J148X1          /dev/sdg  Big5_Data
22    396       0  16%  5.0  WD-WXL1H169E175   /dev/sda  parity
19     72       0   6%  4.0  ZDH26KL5          /dev/sdb  -
29    933       0  12%  3.0  35GM6Y6GS         /dev/sdc  -


The FP column is the estimated probability (in percentage) that the disk
is going to fail in the next year.


Probability that at least one disk is going to fail in the next year is 42%.

Alles anzeigen

Probability that at least one disk is going to fail in the next year is 42%.

Greetings,
Hendrik

tkaiser · 11. Februar 2018

Zitat von henfri

Why do you want to create a raid?

Maybe since it's a concept that has been invented to withstand the fail of a single physical disk?

A RAID5 (while being a really horribly bad idea in 2018 with drives of this size) retains all data when one drive fails. Nothing more, nothing less. If you search for data protection as you correctly mentioned a backup strategy and a technical implementation is needed.

henfri · 11. Februar 2018

Hello,

I am sorry, I read that it was three drives and assumed a raid 0.

Greetings,
Hendrik

Duamer · 11. Februar 2018

Zitat von tkaiser

https://serverfault.com/a/536758

Ah, Ok. I'll figure something else out.

As far as RAID5 or RAID0 being horribly bad ideas, I already have all the data I plan on putting on this stored else where and backed up. The Helios4 is a brand now piece of hardware and I intend to make it a portable server. I wouldn't trust with anything that isn't already properly backed up.

Jetzt mitmachen!