Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: Major
Fix Version/s: Lustre 2.13.0, Lustre 2.12.4
Affects Version/s: Lustre 2.10.0
Labels:
- DoM2
- pfl

Severity:
3
Rank (Obsolete):
9223372036854775807

Appending to a PFL file will cause all layout components to be instantiated because it isn't possible to know what the ending offset is at the time the write is started.

It would be better to avoid this, potentially by locking/instantiating some large(r), but not gigantic range beyond current EOF, and if that fails retry the layout intent? The client must currently be in charge of locking the file during append, so it should know at write time how much of the file to instantiate, and it could retry.

is duplicated by

LU-10665 DoM: append to file causes OST component initialization

Resolved

is related to

LU-9479 sanity test 184d 244: don't instantiate PFL component when taking group lock

Open

LU-10176 Data-on-MDT phase II

Open

LU-13420 append to PFL-file without 'eof' component fails

Open

LU-17694 sanity-compr test_184d: last component index number got assigned even if it was not used after layout swap

Open

LU-15727 lod_get_default_lov_striping() misinterprets composite striping for append

Resolved

LU-17159 Mark file layouts using append striping

Open

LU-19722 PFL: append of PFL file should not use 'append_stripe_count' layout

Open

LU-12738 PFL: append of PFL file should not instantiate full layout

Resolved

is related to

LU-10782 Enable tiny write append for singly striped non-composite file

Open

LU-8998 Progressive File Layout (PFL)

Resolved

(4 is related to, 2 is related to )

Assignee:: Patrick Farrell (Inactive)

Reporter:: Andreas Dilger

Votes:: 0 Vote for this issue

Watchers:: 17 Start watching this issue

Created:: 13/Apr/17 11:14 PM

Updated:: 18/Dec/25 8:22 AM

Resolved:: 20/Sep/19 2:32 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates