Searched refs:lost (Results 1 – 25 of 297) sorted by relevance
12345678910>>...12
... 310 (???) 5Connect to /lost+found? yes 6 7Unconnected directory inode 1520 ...
1 expanding lost+found
4 /lost+found is not a directory (ino=11)7 /lost+found not found. Create? yes11 Connect to /lost+found? yes14 Connect to /lost+found? yes19 Connect to /lost+found? yes24 Connect to /lost+found? yes
5 16 bytes in 1 blocks are possibly lost in loss record ... of ...11 16 bytes in 1 blocks are possibly lost in loss record ... of ...17 16 bytes in 1 blocks are possibly lost in loss record ... of ...23 16 bytes in 1 blocks are possibly lost in loss record ... of ...29 16 bytes in 1 blocks are possibly lost in loss record ... of ...35 16 bytes in 1 blocks are possibly lost in loss record ... of ...41 16 bytes in 1 blocks are definitely lost in loss record ... of ...47 32 (16 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...53 32 (16 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...
5 48 (16 direct, 32 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...11 48 (16 direct, 32 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...17 96 (16 direct, 80 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...23 96 (16 direct, 80 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...
5 16 bytes in 1 blocks are definitely lost in loss record ... of ...11 32 (16 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...17 32 (16 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...
9 10 (+10) bytes in 1 (+1) blocks are definitely lost in loss record ... of ...32 expecting details -10 bytes reachable, +10 bytes lost38 10 (+10) bytes in 1 (+1) blocks are definitely lost in loss record ... of ...44 0 (-10) bytes in 0 (-1) blocks are definitely lost in loss record ... of ...55 32 (+32) bytes in 1 (+1) blocks are definitely lost in loss record ... of ...80 32 bytes in 1 blocks are definitely lost in loss record ... of ...
35 10 bytes in 1 blocks are definitely lost in loss record ... of ...40 10 bytes in 1 blocks are definitely lost in loss record ... of ...45 20 bytes in 1 blocks are definitely lost in loss record ... of ...50 48 (32 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...
5 16 bytes in 1 blocks are definitely lost in loss record ... of ...11 48 (16 direct, 32 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...
7 Entry '..' in /lost+found (11) has deleted/unused inode 2. Clear? yes15 Connect to /lost+found? yes17 /lost+found not found. Create? yes20 Connect to /lost+found? yes
8 /lost+found not found. Create? yes12 Connect to /lost+found? yes17 Connect to /lost+found? yes22 Connect to /lost+found? yes
6 Connect to /lost+found? yes11 Connect to /lost+found? yes16 Connect to /lost+found? yes
13 Connect to /lost+found? yes15 /lost+found not found. Create? yes21 Connect to /lost+found? yes
19 This extension allows an application to force a lost context event.21 becoming lost.36 to become lost. <current> and <other> can each be one of:
1 create lost+found and reconnect lost directory
5 Connect to /lost+found? yes7 /lost+found not found. Create? yes10 Connect to /lost+found? yes
28 # fprintf(stderr, "expecting details +10 bytes lost, +21 bytes reachable\n"); fflush(stderr); bre…56 # fprintf(stderr, "expecting details -10 bytes reachable, +10 bytes lost\n"); fflush(stderr); bre…63 # fprintf(stderr, "expecting details -10 bytes lost, +10 bytes reachable\n"); fflush(stderr); bre…70 # fprintf(stderr, "expecting details 32 (+32) bytes lost, 33 (-32) bytes reachable\n"); fflush(st…
8 10 (+10) bytes in 1 (+1) blocks are definitely lost in loss record ... of ...33 10 (+10) bytes in 1 (+1) blocks are definitely lost in loss record ... of ...38 0 (-10) bytes in 0 (-1) blocks are definitely lost in loss record ... of ...48 32 (+32) bytes in 1 (+1) blocks are definitely lost in loss record ... of ...
15 expecting details -10 bytes reachable, +10 bytes lost33 32 bytes in 1 blocks are definitely lost in loss record ... of ...
16 ReturnedResource() : id(0), sync_point(0), count(0), lost(false) {} in ReturnedResource()20 bool lost; member
10 /lost+found not found. Create? yes16 Connect to /lost+found? yes21 Connect to /lost+found? yes
21 Connect to /lost+found? yes24 Connect to /lost+found? yes27 Connect to /lost+found? yes
17 Setting filetype for entry 'lost+found' in / (2) to 2.33 Setting filetype for entry '.' in /lost+found (11) to 2.34 Setting filetype for entry '..' in /lost+found (11) to 2.
94 int lost,137 int lost,
11 Entry 'lost+found' in / (2) points to inode (11) located in a bad block.15 /lost+found not found. Create? yes