Displaying 3 results from an estimated 3 matches for "dirinfo".
2004 Aug 20
3
Using --keep-dirlinks : recursive symlinks problem
Hello folks,
trying to make use of the new --keep-dirlinks feature for a synch port;
it works excellent but feels incomplete without a way for rsync to
ignore recursive links.
Example:
# ls -la .
total 6
drwxrwxr-x 2 bldmstr staff 512 Aug 16 21:42 .
drwxrwxr-x 8 bldmstr staff 512 Aug 16 21:41 ..
lrwxrwxrwx 1 bldmstr staff 2 Aug 20 12:07 bogus -> ..
if you use
2004 Feb 20
1
ocfs hung
....num_bytes = 0
extent[0].disk_off = 29941760
extent[1].file_off = 0
extent[1].num_bytes = 0
extent[1].disk_off = 0
extent[2].file_off = 0
extent[2].num_bytes = 0
extent[2].disk_off = 0
[root@dc1node1 root]# debugocfs -d /oracle/prod/ /dev/sdd
dirinfo:
Name = /oracle/prod/
curr_master = 0
file_lock = OCFS_DLM_NO_LOCK
oin_node_map = 00000000000000000000000000000000
seq_num = 0
alloc_file_off = 0
alloc_node = 1
free_node_ptr = INVALID_NODE_POINTER
node_disk_off = 29810688...
2007 Apr 07
0
Call for testers w/ using BackupPC (or equivalent)
...e which has been hardlinked, and two of them
are used.
One such filesystem that was reported to me had 88 million inodes, of
which 11 million were files, and 77 million were directories (!). This
meant that e2fsck needed to allocate around 881 megabytes of memory in
one contiguous array for the dirinfo data structures, and two
(approximately) 500 megabyte contiguous arrays for the icount
abstraction.
On a 32-bit processor, especially with shared libraries enabled to
futher reduce the amount of available 3GB address space, e2fsck can very
easily fail to have enough memory. Using a statically-l...