Sponsored Content
Operating Systems Linux File size limitation in the EST 2012 x86_64 GNU/Linux Post 302940086 by MadeInGermany on Wednesday 1st of April 2015 08:20:43 AM
Old 04-01-2015
So this is confirmed, your file system is ext3 with block size 1 KB, and this limits file size to 16 GB.
You have to do your backup to another file system with a bigger block size. Or stream it to a tape.
--
Or recreate the /home file system with a bigger block size.
This would delete all your existing data, so you need a full backup before you do it!
Nowerdays mkfs should default to a 4 KB block size, and file size limit is 64 GB.
Or define explicit options as shown by
Code:
man mkfs.ext3

 

8 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

Size Limitation for a user directory

Hi all, I want to set a size limitation for some user in the system, for an example, each user only have 5MB free space in the system. The user cannot user more than 5 MB space. Is it possible to do this? Thanks! (1 Reply)
Discussion started by: felix_koo
1 Replies

2. HP-UX

HP-UX 11i - File Size Limitation And Number Of Folders Limitation

Hi All, Can anyone please clarify me the following questions: 1. Is there any file size limitation in HP-UX 11i, that I can able to create upto certain size of file (say 2 GB) and not more then that???? 2. At max. how many files we can able to keep inside a folder???? 3. How many... (2 Replies)
Discussion started by: sundeep_mohanty
2 Replies

3. Shell Programming and Scripting

File size limitation of unix sort command.

hi , iam trying to sort millions of records which is delimited and i cant able to use sort command more than 60 million..if i try to do so i got an message stating that "File size limit exceeded",Is there any file size limit for using sort command.. How can i solve this problem. thanks ... (7 Replies)
Discussion started by: cskumar
7 Replies

4. Linux

File size limitation for rcp

Hi I am trying to rcp a file from Solaris box to Linux. When the file size is 2,205,255,047, the rcp fails with the message Jan 10 01:11:53 hqsas167 rsh: pam_authenticate: error Authentication failed However when I rcp a file with smaller size - 9,434,477 - the rcp completes with... (2 Replies)
Discussion started by: schoubal
2 Replies

5. Shell Programming and Scripting

Size limitation in Tar command

Hi to every body there, I am new this forum and this is my first post. I am a new user of Unix, is there any size limitation of files while creating tar file. Thanks in advance (4 Replies)
Discussion started by: Manvar Khan
4 Replies

6. Shell Programming and Scripting

fetchmail - log file size limitation

Hi, I am using fetchmail in my application so as to download mails to the localhost where the application is hosted from the mailserver.Fetchmail is configured as as to run as a daemon polling mails during an interval of 1sec. So my concern here is, during each 2sec it is writing two... (10 Replies)
Discussion started by: DILEEP410
10 Replies

7. Solaris

How to extend 2 GB file size limitation

Hello All, I am using a SunOS machine. My application creates output files for the downstream systems. However output files are restricted to 2GB of file size in SunOS due to which I am forced to create multiple files which is not supported by the downstream due to some limitations. Is... (5 Replies)
Discussion started by: pasupuleti81
5 Replies

8. Linux

File size limitation in Linux

Hi friends, I tried to take a backup of my PC using tar command. But it ended with an error tar: /home/backup/back.tar.gz: Cannot write: No space left on device tar: Error is not recoverable: exiting now But i checked the disk space and there is enough space is available. ]# df Filesystem... (11 Replies)
Discussion started by: siva3492
11 Replies
fsck.ocfs2(8)							OCFS2 Manual Pages						     fsck.ocfs2(8)

NAME
fsck.ocfs2 - Check an OCFS2 file system. SYNOPSIS
fsck.ocfs2 [ -pafFGnuvVy ] [ -b superblock block ] [ -B block size ] device DESCRIPTION
fsck.ocfs2 is used to check an OCFS2 file system. device is the file where the file system is stored (e.g. /dev/sda1). It will almost always be a device file but a regular file will work as well. OPTIONS
-a This option does the same thing as the -p option. It is provided for backwards compatibility only: it is suggested that people use the -p option whenever possible. -b superblock block Normally, fsck.ocfs2 will read the superblock from the first block of the device. This option specifies an alternate block that the superblock should be read from. (Use -r instead of this option.) -B blocksize The block size, specified in bytes, can range from 512 to 4096. A value of 0, the default, is used to indicate that the blocksize should be automatically detected. -D Optimize directories in filesystem. This option causes fsck.ocfs2 to coalesce the directory entries in order to improve the filesys- tem performance. -f Force checking even if the file system is clean. -F By default fsck.ocfs2 will check with the cluster services to ensure that the volume is not in-use (mounted) on any node in the cluster before proceeding. -F skips this check and should only be used when it can be guaranteed that the volume is not mounted on any node in the cluster. WARNING: If the cluster check is disabled and the volume is mounted on one or more nodes, file system cor- ruption is very likely. If unsure, do not use this option. -G Usually fsck.ocfs2 will silently assume inodes whose generation number does not match the generation number of the super block are unused inodes. This option causes fsck.ocfs2 to ask the user if these inodes should in fact be marked unused. -n Give the 'no' answer to all questions that fsck will ask. This guarantees that the file system will not be modified and the device will be opened read-only. The output of fsck.ocfs2 with this option can be redirected to produce a record of a file system's faults. -p Automatically repair ("preen") the file system. This option will cause fsck.ocfs2 to automatically fix any problem that can be safely corrected without human intervention. If there are problems that require intervention, the descriptions will be printed and fsck.ocfs2 will exit with the value 4 logically or'd into the exit code. (See the EXIT CODE section.) This option is normally used by the system's boot scripts. -r backup-number mkfs.ocfs2 makes upto 6 backup copies of the superblock at offsets 1G, 4G, 16G, 64G, 256G and 1T depending on the size of the vol- ume. Use this option to specify the backup, 1 thru 6, to use to recover the superblock. -y Give the 'yes' answer to all questions that fsck will ask. This will repair all faults that fsck.ocfs2 finds but will not give the operator a chance to intervene if fsck.ocfs2 decides that it wants to drastically repair the file system. -v This option causes fsck.ocfs2 to produce a very large amount of debugging output. -V Print version information and exit. EXIT CODE
The exit code returned by fsck.ocfs2 is the sum of the following conditions: 0 - No errors 1 - File system errors corrected 2 - File system errors corrected, system should be rebooted 4 - File system errors left uncorrected 8 - Operational error 16 - Usage or syntax error 32 - fsck.ocfs2 canceled by user request 128 - Shared library error SEE ALSO
mkfs.ocfs2(8) debugfs.ocfs2(8) tunefs.ocfs2(8) mounted.ocfs2(8) ocfs2console(8) o2cb(7) AUTHORS
Oracle Corporation. This man page entry derives some text, especially the exit code summary, from e2fsck(8) by Theodore Y. Ts'o <tytso@mit.edu>. COPYRIGHT
Copyright (C) 2004, 2010 Oracle. All rights reserved. Version 1.6.4 September 2010 fsck.ocfs2(8)
All times are GMT -4. The time now is 05:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy